[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28626.1457348905@warthog.procyon.org.uk>
Date: Mon, 07 Mar 2016 11:08:25 +0000
From: David Howells <dhowells@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: dhowells@...hat.com, Herbert Xu <herbert@...dor.apana.org.au>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: manual merge of the crypto tree with the net-next tree
Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Today's linux-next merge of the crypto tree got a conflict in:
>
> net/rxrpc/rxkad.c
>
> between commit:
>
> 0d12f8a4027d ("rxrpc: Keep the skb private record of the Rx header in host byte order")
>
> from the net-next tree and commit:
>
> 1afe593b4239 ("rxrpc: Use skcipher")
>
> from the crypto tree.
What's the best way to deal with this? Should I take Herbert's
[PATCH 18/26] rxrpc: Use skcipher
patch into my rxrpc tree also and pass it on to Dave?
David
Powered by blists - more mailing lists