Home Home > GIT Browse > SLE11-SP4
diff options
authorMichal Hocko <mhocko@suse.com>2019-01-14 13:17:30 +0100
committerMichal Hocko <mhocko@suse.com>2019-01-14 13:17:30 +0100
commit8988d6f36e5ba31151c638aef6e201429c42c193 (patch)
parentf939fdb1e32fb4519afd49c8f3e6eee71b183240 (diff)
parent684221f1c7f6bbfa7dfad1f639baa61316904c4f (diff)
Merge remote-tracking branch 'origin/users/pmladek/SLE11-SP4/for-next' into users/mhocko/SLE11-SP4/for-next
1 files changed, 4 insertions, 0 deletions
diff --git a/blacklist.conf b/blacklist.conf
index 3acae8e53e..4860d16c69 100644
--- a/blacklist.conf
+++ b/blacklist.conf
@@ -188,6 +188,7 @@ bfedb589252c01fa505ac9f6f2a3d5d68d707ef4 # bnc1044228
c65540453e150844367ffe98e45d5175181b2ec1 # unsupported platform
a9f8553e935f26cb5447f67e280946b0923cd2dc # depends on features we don't have
2bdd713b92a9cade239d3c7d15205a09f556624d # bsc#1066471 - crypto_memneq() only on >= v3.13-rc2
+b1e3874c75ab15288f573b3532e507c37e8e7656 # pcrypt: internal API, used correctly everywhere; bsc#1120950
2b1be689f3aadcfe0a768314c80e43483c784659 # non-trivial backport, visible only when debugging with a particular early consoles, did not reported for years
1f6ae47ecff7f23da73417e068018b311f3b5583 # PCI ASPM fix - not applicable cleanly
14fc42fa1b3e7ea5160c84d0e686a3a0c1ffe619 # non-critical perf tools fix, no backport without customer bug
@@ -323,3 +324,6 @@ acceb72e90624ec6c3f2fc62e72dab892cd075da # duplicate of 82cc4fc2e70ec5baeff8f776
6b7e633fe9c24682df550e5311f47fb524701586 # optimization
1fe4293f4b8de75824935f8d8e9a99c7fc6873da # function graph tracer is disabled
8a03e81cb14712f986c5d5fa42a30ff2cbe3237c # no powernv code on SLE11
+b33c8ff4431a343561e2319f17c14286f2aa52e2 # tracing: link error with some gcc version or some configurations
+9b94a8fba501f38368aef6ac1b30e7335252a220 # ring_buffer: less critical on SLE11 because there is used "unsigned" instead of "int" for the buffer size; need a root; would need > 8TB memory per-CPU even when it works
+688b744d8bc84dc5cc646e97509113dc5e8818ed # kgdb: very old problem; might be visible only when debugging int3 context on x86_64