[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090812.173325.255498124.davem@davemloft.net>
Date: Wed, 12 Aug 2009 17:33:25 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: sfr@...b.auug.org.au
Cc: tglx@...utronix.de, mingo@...e.hu, hpa@...or.com,
peterz@...radead.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, arnd@...db.de, jengelh@...ozas.de
Subject: Re: linux-next: manual merge of the tip tree with the net tree
From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Fri, 7 Aug 2009 16:47:05 +1000
> Today's linux-next merge of the tip tree got a conflict in
> arch/x86/include/asm/socket.h between commits
> 49c794e94649020248e37b78db16cd25bad38b4f ("net: implement a SO_PROTOCOL
> getsockoption") and 0d6038ee76f2e06b79d0465807f67e86bf4025de ("net:
> implement a SO_DOMAIN getsockoption") from the net tree and commit
> 73a2d096fdf23aa841f7595d114a11ec85a85e4d ("x86: remove all now-duplicate
> header files") from the tip tree.
>
> The latter change supercedes the former ones, so I used the latter.
That should be the correct merge resolution, thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists