From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto List <linux-crypto@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: linux-next: manual merge of the crypto tree with the jc_docs tree
Date: Tue, 4 Aug 2020 08:15:25 +1000 [thread overview]
Message-ID: <20200804081525.5df251b2@canb.auug.org.au> (raw)
In-Reply-To: <20200724130951.5b99a9c9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]
Hi all,
On Fri, 24 Jul 2020 13:09:51 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the crypto tree got a conflict in:
>
> Documentation/crypto/api-intro.rst
>
> between commit:
>
> 5846551bb147 ("docs: crypto: convert api-intro.txt to ReST format")
>
> from the jc_docs tree and commit:
>
> 9332a9e73918 ("crypto: Replace HTTP links with HTTPS ones")
>
> 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.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc Documentation/crypto/api-intro.rst
> index bcff47d42189,40137f93e04f..000000000000
> --- a/Documentation/crypto/api-intro.rst
> +++ b/Documentation/crypto/api-intro.rst
> @@@ -159,31 -146,31 +159,31 @@@ Credit
> The following people provided invaluable feedback during the development
> of the API:
>
> - Alexey Kuznetzov
> - Rusty Russell
> - Herbert Valerio Riedel
> - Jeff Garzik
> - Michael Richardson
> - Andrew Morton
> - Ingo Oeser
> - Christoph Hellwig
> + - Alexey Kuznetzov
> + - Rusty Russell
> + - Herbert Valerio Riedel
> + - Jeff Garzik
> + - Michael Richardson
> + - Andrew Morton
> + - Ingo Oeser
> + - Christoph Hellwig
>
> Portions of this API were derived from the following projects:
> -
> +
> Kerneli Cryptoapi (http://www.kerneli.org/)
> - Alexander Kjeldaas
> - Herbert Valerio Riedel
> - Kyle McMartin
> - Jean-Luc Cooke
> - David Bryson
> - Clemens Fruhwirth
> - Tobias Ringstrom
> - Harald Welte
> + - Alexander Kjeldaas
> + - Herbert Valerio Riedel
> + - Kyle McMartin
> + - Jean-Luc Cooke
> + - David Bryson
> + - Clemens Fruhwirth
> + - Tobias Ringstrom
> + - Harald Welte
>
> and;
> -
> +
> - Nettle (http://www.lysator.liu.se/~nisse/nettle/)
> + Nettle (https://www.lysator.liu.se/~nisse/nettle/)
> - Niels Möller
> + - Niels Möller
>
> Original developers of the crypto algorithms:
>
This is now a conflict between the jc_docs tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-08-03 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 3:09 linux-next: manual merge of the crypto tree with the jc_docs tree Stephen Rothwell
2020-08-03 22:15 ` Stephen Rothwell [this message]
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=20200804081525.5df251b2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=corbet@lwn.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).