From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754528Ab0I2N41 (ORCPT ); Wed, 29 Sep 2010 09:56:27 -0400 Received: from zone0.gcu-squad.org ([212.85.147.21]:24934 "EHLO services.gcu-squad.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751680Ab0I2N4Z (ORCPT ); Wed, 29 Sep 2010 09:56:25 -0400 Date: Wed, 29 Sep 2010 15:56:09 +0200 From: Jean Delvare To: matt mooney Cc: kernel-janitors@vger.kernel.org, "Ben Dooks (embedded platforms)" , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org Subject: Re: [PATCH 05/24] i2c: change to new flag variable Message-ID: <20100929155609.00a70ee0@endymion.delvare> In-Reply-To: <20100926180726.GD8191@haskell.muteddisk.com> References: <9968d4260be8850200cc9c7dfe08addf611468b4.1285355033.git.mfm@muteddisk.com> <036514b5dd23c5af14303519d79d60d79adccbee.1285355033.git.mfm@muteddisk.com> <20100925132611.03ef0882@endymion.delvare> <20100926021217.GC8191@haskell.muteddisk.com> <20100926092931.68980448@endymion.delvare> <20100926180726.GD8191@haskell.muteddisk.com> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.20.1; x86_64-unknown-linux-gnu) Mime-Version: 1.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 On Sun, 26 Sep 2010 11:07:26 -0700, matt mooney wrote: > On 09:29 Sun 26 Sep , Jean Delvare wrote: > > On Sat, 25 Sep 2010 19:12:17 -0700, matt mooney wrote: > > > Sam had implemented these newer style flag variables a while back as an > > > eloquent way of handling conditional flags. A lot of newer (and some older) > > > modules and subsystems were using them already, so to provide uniformity and for > > > an eventual removal of the deprecated flags, I converted all remaining instances > > > to the newer style. (IMHO, I think it flows better with the way the rest of the > > > build system works.) > > > > Fine with me. What's the planned merge path for this patch? Will you > > push all the patches upstream yourself, or do you expect me to pick > > this one? > > I was hoping subsystem maintainers would pick them up, but a lot of the patches > have been acked without being applied. My new plan is to have the unapplied ones > go through the kbuild tree. So you can either pick it up or just ack it. I've picked the patch, it's now in my i2c tree, scheduled for merge in 2.6.37. -- Jean Delvare