From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean-Christophe PLAGNIOL-VILLARD Subject: Re: [PATCH] mmc: at91-mci: remove driver Date: Tue, 30 Oct 2012 16:43:09 +0100 Message-ID: <20121030154309.GD19021@game.jcrosoft.org> References: <1351520875-31891-1-git-send-email-ludovic.desroches@atmel.com> <87625txrou.fsf@octavius.laptop.org> <20121030150113.GB19021@game.jcrosoft.org> <87ehkgov3a.fsf@octavius.laptop.org> <20121030153350.GC19021@game.jcrosoft.org> <87a9v4otqh.fsf@octavius.laptop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <87a9v4otqh.fsf@octavius.laptop.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Chris Ball Cc: nicolas.ferre@atmel.com, ludovic.desroches@atmel.com, linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-mmc@vger.kernel.org On 11:38 Tue 30 Oct , Chris Ball wrote: > Hi, > > On Tue, Oct 30 2012, Jean-Christophe PLAGNIOL-VILLARD wrote: > > On 11:09 Tue 30 Oct , Chris Ball wrote: > >> Hi, > >> > >> On Tue, Oct 30 2012, Jean-Christophe PLAGNIOL-VILLARD wrote: > >> >> Thanks! Pushed to mmc-next for 3.8. > >> > > >> > if you don't mind I prefer to take it via at91 > >> > > >> > I've a patch series that cleanup the platform_data it's difficult to merge > >> > with this one > >> > >> Hm, I don't understand why it should be difficult to merge. Is it > >> because this patch modifies arch/arm/mach-at91/include/mach/board.h? > >> > >> If so, sounds like we should just take that change out of this patch > >> and have it go into your platform data cleanup patch, and then I can > >> merge the drivers/mmc change independently? Let me know what you think. > > I'm modifing and moiving the board.h so this file will not exist anymore > > > > and the platform data are not anymore in arch/arm/mach-at91/include/mach/board.h > > Can we take the modification of board.h out of this patch, then, > leaving just the drivers/mmc/ changes? If you really insist but for changelog history and bisectable I'll prefer to do not do so Best Regards, J. From mboxrd@z Thu Jan 1 00:00:00 1970 From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD) Date: Tue, 30 Oct 2012 16:43:09 +0100 Subject: [PATCH] mmc: at91-mci: remove driver In-Reply-To: <87a9v4otqh.fsf@octavius.laptop.org> References: <1351520875-31891-1-git-send-email-ludovic.desroches@atmel.com> <87625txrou.fsf@octavius.laptop.org> <20121030150113.GB19021@game.jcrosoft.org> <87ehkgov3a.fsf@octavius.laptop.org> <20121030153350.GC19021@game.jcrosoft.org> <87a9v4otqh.fsf@octavius.laptop.org> Message-ID: <20121030154309.GD19021@game.jcrosoft.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 11:38 Tue 30 Oct , Chris Ball wrote: > Hi, > > On Tue, Oct 30 2012, Jean-Christophe PLAGNIOL-VILLARD wrote: > > On 11:09 Tue 30 Oct , Chris Ball wrote: > >> Hi, > >> > >> On Tue, Oct 30 2012, Jean-Christophe PLAGNIOL-VILLARD wrote: > >> >> Thanks! Pushed to mmc-next for 3.8. > >> > > >> > if you don't mind I prefer to take it via at91 > >> > > >> > I've a patch series that cleanup the platform_data it's difficult to merge > >> > with this one > >> > >> Hm, I don't understand why it should be difficult to merge. Is it > >> because this patch modifies arch/arm/mach-at91/include/mach/board.h? > >> > >> If so, sounds like we should just take that change out of this patch > >> and have it go into your platform data cleanup patch, and then I can > >> merge the drivers/mmc change independently? Let me know what you think. > > I'm modifing and moiving the board.h so this file will not exist anymore > > > > and the platform data are not anymore in arch/arm/mach-at91/include/mach/board.h > > Can we take the modification of board.h out of this patch, then, > leaving just the drivers/mmc/ changes? If you really insist but for changelog history and bisectable I'll prefer to do not do so Best Regards, J.