From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: linux-next: manual merge of the crypto tree with the kbuild tree
Date: Tue, 11 Apr 2017 15:02:50 +1000 [thread overview]
Message-ID: <20170411150250.49996951@canb.auug.org.au> (raw)
In-Reply-To: <20170411024215.GA10664@gondor.apana.org.au>
Hi Herbert,
On Tue, 11 Apr 2017 10:42:15 +0800 Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> Actually the patch in the kbuild tree should be reverted because
> we have now increased the in-kernel length limit and this must not
> be directly exposed to user-space or it'll break compatibility.
So basically we need CRYPTO_MAX_ALG_NAME to be 64 in the exported
header but 128 in the kernel header? In which case the kbuild patch
needs to be changed not removed. Or the merge resolution needs to be
cleverer.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-04-11 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 0:21 linux-next: manual merge of the crypto tree with the kbuild tree Stephen Rothwell
2017-04-11 2:42 ` Herbert Xu
2017-04-11 5:02 ` Stephen Rothwell [this message]
2017-04-11 5:12 ` Herbert Xu
2017-04-11 6:34 ` Masahiro Yamada
2017-04-11 6:40 ` Herbert Xu
2017-04-11 7:00 ` Masahiro Yamada
2017-04-11 7:19 ` Herbert Xu
2017-04-11 7:51 ` Masahiro Yamada
2017-04-11 9:22 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170411150250.49996951@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.