[lkml]   [2018]   [Oct]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subjectlinux-next: manual merge of the crypto tree with the compiler-attributes tree
Hi all,

Today's linux-next merge of the crypto tree got a conflict in:


between commit:

a3f8a30f3f00 ("Compiler Attributes: use feature checks instead of version checks")

from the compiler-attributes tree and commit:

f3569fd613f6 ("crypto: shash - Remove VLA usage in unaligned hashing")

from the crypto tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

A removed line was moved to a new file, so I have applied the following
merge fix patch from today:

From: Stephen Rothwell <>
Date: Mon, 8 Oct 2018 11:44:24 +1100
Subject: [PATCH] crypto: fixup for movement of __aligned_largest

Signed-off-by: Stephen Rothwell <>
include/linux/compiler_attributes.h | 1 -
1 file changed, 1 deletion(-)

diff --git a/include/linux/compiler_attributes.h b/include/linux/compiler_attributes.h
index 6b28c1b7310c..9db94801c780 100644
--- a/include/linux/compiler_attributes.h
+++ b/include/linux/compiler_attributes.h
@@ -49,7 +49,6 @@
* gcc:
#define __aligned(x) __attribute__((__aligned__(x)))
-#define __aligned_largest __attribute__((__aligned__))

* Note: users of __always_inline currently do not write "inline" themselves,
Stephen Rothwell
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2018-10-08 02:48    [W:0.039 / U:1.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site