linux-kernel - Re: linux-next: manual merge of the vhost tree with the hexagon tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20111130205030.ed1e48bf5588a1aeeb2f4a3d@canb.auug.org.au>
Date:	Wed, 30 Nov 2011 20:50:30 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Richard Kuo <rkuo@...eaurora.org>
Cc:	"Michael S. Tsirkin" <mst@...hat.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: manual merge of the vhost tree with the hexagon
 tree

Hi Richard,

On Wed, 30 Nov 2011 00:45:53 -0600 Richard Kuo <rkuo@...eaurora.org> wrote:
>
> On Tue, Nov 29, 2011 at 02:22:59PM +1100, Stephen Rothwell wrote:
> > 
> > Today's linux-next merge of the vhost tree got a conflict in
> > arch/hexagon/Kconfig between commit 5237bae0d8c9 ("various Kconfig
> > cleanup and old platform build code removal") from the hexagon tree and
> > commit4673ca8eb369  ("lib: move GENERIC_IOMAP to lib/Kconfig") from the
> > vhost tree.
> > 
> > Just context changes.  I fixed it up (see below) and can carry the fix as
> > necessary.
> 
> I was figuring this would happen.  What would be the best way for me to
> fix this?  Maybe rebase my patches on top of the vhost tree?

No, just ignore it.  Linus will fix it up when he merges the trees into
his.  Its pretty trivial anyway.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped