Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754126AbZKQIAo (ORCPT ); Tue, 17 Nov 2009 03:00:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753031AbZKQIAk (ORCPT ); Tue, 17 Nov 2009 03:00:40 -0500 Received: from mo-p00-ob.rzone.de ([81.169.146.161]:43514 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbZKQIAj (ORCPT ); Tue, 17 Nov 2009 03:00:39 -0500 X-RZG-AUTH: :I2ANY0W6W/eA95XfH/xfO6gOxLxTty/udEMngcJ/VAKW22CjDNNVyn5BfohAbc5z X-RZG-CLASS-ID: mo00 Message-ID: <4B025812.6060807@hartkopp.net> Date: Tue, 17 Nov 2009 09:00:18 +0100 From: Oliver Hartkopp User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: Stephen Rothwell CC: David Miller , netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Wolfram Sang , Christian Pellegrin , Wolfgang Grandegger , Anant Gole Subject: Re: linux-next: manual merge of the net tree with the net-current tree References: <20091117131637.3a35f898.sfr@canb.auug.org.au> In-Reply-To: <20091117131637.3a35f898.sfr@canb.auug.org.au> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1467 Lines: 42 Hello Stephen, Stephen Rothwell wrote: > Today's linux-next merge of the net tree got a conflict in > drivers/net/can/Kconfig between commit > b93cf3f0bb45560d2ce62bdcc2181c40660cfdbf ("can: Fix driver Kconfig > structure") from the net-current tree Indeed this cleanup was made in net-2.6 to fix the Kconfig structure before 2.6.32 is finalized. The commits > 3758bf25db8caeec667e4e56e030da0ec3060529 ("can: add TI CAN (HECC) > driver"), e0000163e30eeb112b41486ea113fd54f64e1f17 ("can: Driver for the > Microchip MCP251x SPI CAN controllers") and > afa17a500a3667f66df450100538d06769529bba ("net/can: add driver for mscan > family & mpc52xx_mscan") from the net tree. added Kconfig entries right behind the CAN_AT91 driver - and that's because the net-2.6 patch "can: Fix driver Kconfig structure" refuses to apply cleanly on net-next-2.6 ... > > I fixed it up (see below) and can carry the fix for a while. (I am not > sure the fix is entirely correct.) > Yes. You only added the new Kconfig entries (for CAN_TI_HECC, CAN_MCP251X, CAN_MSCAN, ...) to the patch "can: Fix driver Kconfig structure", right? These are the only added items in drivers/net/can/Kconfig from net-2.6 to net-next-2.6. Thanks, Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/