Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754970AbbFKVqf (ORCPT ); Thu, 11 Jun 2015 17:46:35 -0400 Received: from down.free-electrons.com ([37.187.137.238]:36363 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753370AbbFKVqc (ORCPT ); Thu, 11 Jun 2015 17:46:32 -0400 Date: Thu, 11 Jun 2015 23:46:29 +0200 From: Alexandre Belloni To: "Opensource [Steve Twiss]" Cc: Lee Jones , LINUXKERNEL , Samuel Ortiz , Alessandro Zummo , DEVICETREE , David Dajun Chen , Dmitry Torokhov , Ian Campbell , Kumar Gala , LINUXINPUT , LINUXWATCHDOG , Liam Girdwood , Mark Brown , Mark Rutland , Pawel Moll , RTCLINUX , Rob Herring , Support Opensource , Wim Van Sebroeck Subject: Re: [rtc-linux] RE: [PATCH V3 1/4] mfd: da9062: DA9062 MFD core driver Message-ID: <20150611214629.GA3890@piout.net> References: <20150526161024.GQ11677@x1> <6ED8E3B22081A4459DAC7699F3695FB7014B22F4C4@SW-EX-MBX02.diasemi.com> <20150611085653.GG2982@x1> <6ED8E3B22081A4459DAC7699F3695FB7014B22F4DC@SW-EX-MBX02.diasemi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7014B22F4DC@SW-EX-MBX02.diasemi.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2342 Lines: 60 Hi, On 11/06/2015 at 09:27:45 +0000, Opensource [Steve Twiss] wrote : > > Thanks for replying so quickly. > > > I'm still not particularly happy with this. Can yo speak to your H/W > > guys and get them to change their scripts to output sensible header > > files? > > Ah. Ok. > > For our side, the generated headers might not just be used for Linux. I've > just discussed this with my colleagues and they will need it to remain. > So I guess internally we will keep the headers like this, but as it enters > my submission process I can change it for the Linux community. > > > To be honest, it's probably not a blocker for acceptance, but if someone > > writes a patch next week to change all of the (0x01 << X) lines to > > start using the BIT() macro, I will accept it. Better to influenced > > your guys so you are not overly inconvenienced. > > Yep: I will change this BIT() macro for the submissions in future. > Depending on the next step, I will send a patch to this or update the submission > if there are further comments on this patch set. > Maybe a good solution would be to define BIT() at the top of your generated header so that you simply have to remove it or replace it with the proper include before mainline submission. > > FWIW, when upstreaming code, the excuse "someone else wrote it", has > > never been a good one to use on the lists. Believe me, I've > > tried. ;) > > heh okay :) > > Regards, > Steve > > -- > -- > You received this message because you are subscribed to "rtc-linux". > Membership options at http://groups.google.com/group/rtc-linux . > Please read http://groups.google.com/group/rtc-linux/web/checklist > before submitting a driver. > --- > You received this message because you are subscribed to the Google Groups "rtc-linux" group. > To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- 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/