From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Biggers <ebiggers@google.com>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: linux-next: manual merge of the staging tree with the crypto tree
Date: Thu, 16 Aug 2018 09:49:03 +1000 [thread overview]
Message-ID: <20180816094903.7744e6b0@canb.auug.org.au> (raw)
In-Reply-To: <20180709141510.19e1a851@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Hi all,
On Mon, 9 Jul 2018 14:15:10 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/skein/skein_generic.c
>
> between commit:
>
> e50944e219f9 ("crypto: shash - remove useless setting of type flags")
>
> from the crypto tree and commit:
>
> ee55fe552fcd ("staging/skein: Remove Skein and Threefish code")
>
> from the staging tree.
>
> I fixed it up (I removed the file) 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.
This is now a conflict between Linus' tree and the staging tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-15 23:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 4:15 linux-next: manual merge of the staging tree with the crypto tree Stephen Rothwell
2018-08-15 23:49 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-18 5:21 Stephen Rothwell
2020-09-18 5:41 ` Herbert Xu
2020-09-18 7:49 ` Greg KH
2020-09-18 7:50 ` Herbert Xu
2020-09-18 8:05 ` Greg KH
2020-09-20 14:01 ` Greg KH
2018-03-15 6:58 Stephen Rothwell
2018-03-15 10:18 ` Greg KH
2016-02-22 3:55 Stephen Rothwell
2016-02-23 1:36 ` Greg KH
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=20180816094903.7744e6b0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiggers@google.com \
--cc=greg@kroah.com \
--cc=herbert@gondor.apana.org.au \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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