summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-11-23 16:36:35 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2013-11-23 16:36:35 -0800
commit34ef7bd3823bf4401bf8f1f855e1bc77b82b1a43 (patch)
tree80b9e7de72353048b5e933d634d64bd14d0eb00c /crypto
parent26b265cd29dde56bf0901c421eabc7ae815f38c4 (diff)
downloadlinux-stable-34ef7bd3823bf4401bf8f1f855e1bc77b82b1a43.tar.gz
linux-stable-34ef7bd3823bf4401bf8f1f855e1bc77b82b1a43.tar.bz2
linux-stable-34ef7bd3823bf4401bf8f1f855e1bc77b82b1a43.zip
Revert "ima: define '_ima' as a builtin 'trusted' keyring"
This reverts commit 217091dd7a7a1bdac027ddb7c5a25f6ac0b8e241, which caused the following build error: security/integrity/digsig.c:70:5: error: redefinition of ‘integrity_init_keyring’ security/integrity/integrity.h:149:12: note: previous definition of ‘integrity_init_keyring’ w security/integrity/integrity.h:149:12: warning: ‘integrity_init_keyring’ defined but not used reported by Krzysztof Kolasa. Mimi says: "I made the classic mistake of requesting this patch to be upstreamed at the last second, rather than waiting until the next open window. At this point, the best course would probably be to revert the two commits and fix them for the next open window" Reported-by: Krzysztof Kolasa <kkolasa@winsoft.pl> Acked-by: Mimi Zohar <zohar@linux.vnet.ibm.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions