Thread (5 messages) 5 messages, 2 authors, 2013-09-27

Re: linux-next: manual merge of the ipsec-next tree with the net-next tree

From: Stephen Rothwell <hidden>
Date: 2013-09-27 02:01:24
Also in: linux-next, lkml

Hi Steffen,

On Wed, 25 Sep 2013 07:29:23 +0200 Steffen Klassert [off-list ref] wrote:
On Wed, Sep 25, 2013 at 09:59:19AM +1000, Stephen Rothwell wrote:
quoted
On Tue, 24 Sep 2013 12:25:05 +0200 Steffen Klassert [off-list ref] wrote:
quoted
On Tue, Sep 24, 2013 at 12:16:29PM +1000, Stephen Rothwell wrote:
quoted
Today's linux-next merge of the ipsec-next tree got a conflict in
include/net/xfrm.h between commit d511337a1eda ("xfrm.h: Remove extern
from function prototypes") from the net-next tree and commit aba826958830
("{ipv4,xfrm}: Introduce xfrm_tunnel_notifier for xfrm tunnel mode
callback") from the ipsec-next tree.
Thanks for the information, I'll do a rebase of the ipsec-next
tree tomorrow.
Did you miss the end of the next paragraph:  "no action is required"?
Dave can fix this up (like I did) when he merges your tree into his.
I applied this patch shortly before the merge window opened, it is a left
over from the last develpoment cycle. I already rebased my tree onto
net-next in the past if that happened, even if there were no merge
conflicts. I did that just to see if everything still works. But I
could also do a test merge to see if everything still works and ask
to pull without a rebase then if this is the prefered way. Would make
my life easier :)
That would be up to Dave ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

Attachments

  • (unnamed) [application/pgp-signature] 836 bytes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help