linux-kernel - Re: linux-next: manual merge of the i2c tree with the arm-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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090506071547.GA29466@flint.arm.linux.org.uk>
Date:	Wed, 6 May 2009 08:15:48 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Jean Delvare <khali@...ux-fr.org>, linux-next@...r.kernel.org,
	Nicolas Pitre <nico@....org>,
	Wolfram Sang <w.sang@...gutronix.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the i2c tree with the arm-current
	tree

On Wed, May 06, 2009 at 01:10:31PM +1000, Stephen Rothwell wrote:
> Hi Jean,
> 
> Today's linux-next merge of the i2c tree got a conflict in
> arch/arm/configs/kirkwood_defconfig arch/arm/configs/mv78xx0_defconfig
> arch/arm/configs/orion5x_defconfig between various commits from the
> arm-current tree and commit c637675d24618d8e0afe344096a1ad96986c4f50
> ("i2c/chips: Move max6875 to drivers/misc/eeprom") from the i2c tree.

Since defconfig updates are always going to create lots of noise, and
the files are normally out of date, the *only* sensible way to handle
updates is to have one tree dealing with them per architecture.

Spreading them across multiple trees and then expecting merges to sort
out the resulting mess is unreasonable; they just change far too much
when updates happen.  Moreover, defconfig updates should be in their
own separate commit and not combined with other changes.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
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/