From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: [PATCH 042/199] Documentation/i2c/busses/i2c-ali1535: Checkpatch cleanup Date: Sun, 23 May 2010 14:56:19 -0700 Message-ID: <20100523145619.db187124.rdunlap@xenotime.net> References: <1274644605-25181-1-git-send-email-andrea.gelmini@gelma.net> <1274644605-25181-14-git-send-email-andrea.gelmini@gelma.net> <20100523231455.74927a98@hyperion.delvare> <20100523143427.3b179427.rdunlap@xenotime.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: Andrea Gelmini Cc: Jean Delvare , "Ben Dooks (embedded platforms)" , linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Sun, 23 May 2010 23:50:23 +0200 Andrea Gelmini wrote: > 2010/5/23 Randy Dunlap : > > If they are merged into one patch per subsystem, I'll likely merge = them > > if subsystem owners do not do so. =A0As is, I won't. =A0It's just t= oo much work > > for too little gain. >=20 > I agree. > If you prefer I can check all Documentation/ and put patches in big > chunks (trailing spaces, and so on). They don't even have to be trailing-spaces-specific (for example). Just all of Documentation/ as one patch or multiple Documentation// patches. I think that I would prefer one patch per subsystem. thanks, --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your cod= e ***