linux-kernel - linux-next: bad merge in driver-core.current 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-next>] [day] [month] [year] [list]

Message-Id: <20130104100540.3671b46eb7de73374db7f786@canb.auug.org.au>
Date:	Fri, 4 Jan 2013 10:05:40 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Greg KH <greg@...ah.com>
Cc:	Linus <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Bill Pemberton <wfp5p@...ginia.edu>
Subject: linux-next: bad merge in driver-core.current tree

Hi Greg,

Happy New year!  ;-)

Today you added a merge of v3.8-rc2 to the driver-core.current tree.  It
added the file drivers/i2c/Module.symvers which is a generated file :-(

Please consider rebuilding your tree to get rid of it.  Also, you might
consider removing all the patches that remove the __dev* stuff as they
are really not urgent, cause many conflicts (and will continue to do so)
and most (if not all) are not acked by the maintainers of the subsystems
that they should be applied to (did you send your revised versions of
Bill's patches to those maintainers?).  You might consider sending
separate patches to fix the coding style problems after Bill's patches
rather than modifying Bill's patches as some of Bill's patches are
turning up in other subsystems (as happened with i2c).
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped