From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephen Rothwell <sfr@canb.auug.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 13:12:28 +0800 [thread overview]
Message-ID: <20170411051228.GA10951@gondor.apana.org.au> (raw)
In-Reply-To: <20170411150250.49996951@canb.auug.org.au>
On Tue, Apr 11, 2017 at 03:02:50PM +1000, Stephen Rothwell wrote:
>
> 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.
Actually the kbuild patch just needs to be reverted. We should
not export CRYPTO_MAX_ALG_NAME at all. Each user-space interface
that uses it already has its own limit and should not refer to the
in-kernel value.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2017-04-11 5:12 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
2017-04-11 5:12 ` Herbert Xu [this message]
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=20170411051228.GA10951@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox