public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: matt mooney <mfm@muteddisk.com>
Cc: kernel-janitors@vger.kernel.org,
	"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
	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
Date: Wed, 29 Sep 2010 15:56:09 +0200	[thread overview]
Message-ID: <20100929155609.00a70ee0@endymion.delvare> (raw)
In-Reply-To: <20100926180726.GD8191@haskell.muteddisk.com>

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

  reply	other threads:[~2010-09-29 13:56 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 19:17 [PATCH 01/24] base: change to new flag variable matt mooney
2010-09-24 19:17 ` [PATCH 02/24] char: " matt mooney
2010-09-24 19:17 ` [PATCH 03/24] dma: " matt mooney
2010-09-24 19:17 ` [PATCH 04/24] hwmon: " matt mooney
2010-09-24 23:54   ` [lm-sensors] " Guenter Roeck
2010-09-27 15:04   ` Valdis.Kletnieks
2010-09-27 17:23     ` matt mooney
2010-09-24 19:17 ` [PATCH 05/24] i2c: " matt mooney
2010-09-25 11:26   ` Jean Delvare
2010-09-26  2:12     ` matt mooney
2010-09-26  7:29       ` Jean Delvare
2010-09-26 18:07         ` matt mooney
2010-09-29 13:56           ` Jean Delvare [this message]
2010-09-24 19:17 ` [PATCH 06/24] ide: " matt mooney
2010-09-24 20:01   ` David Miller
2010-09-24 19:17 ` [PATCH 07/24] ieee802154: " matt mooney
2010-09-26 10:31   ` Dmitry Eremin-Solenikov
2010-09-24 19:17 ` [PATCH 08/24] infiniband: " matt mooney
2010-09-24 19:17 ` [PATCH 09/24] input: " matt mooney
2010-09-24 19:17 ` [PATCH 10/24] isdn: " matt mooney
2010-09-24 20:01   ` David Miller
2010-09-24 19:17 ` [PATCH 11/24] memstick: " matt mooney
2010-09-24 19:17 ` [PATCH 12/24] message: " matt mooney
2010-09-24 19:17 ` [PATCH 13/24] misc: " matt mooney
2010-09-28 13:02   ` Michał Mirosław
2010-09-29 22:55     ` matt mooney
2010-09-24 19:17 ` [PATCH 14/24] mmc: " matt mooney
2010-09-24 19:17 ` [PATCH 15/24] net: " matt mooney
2010-09-24 19:25   ` John W. Linville
2010-09-24 20:01   ` David Miller
2010-09-24 19:17 ` [PATCH 16/24] pci: " matt mooney
2010-10-15 19:54   ` Jesse Barnes
2010-09-24 19:17 ` [PATCH 17/24] power: " matt mooney
2010-09-24 19:17 ` [PATCH 18/24] pps: " matt mooney
2010-09-24 19:17 ` [PATCH 19/24] rapidio: " matt mooney
2010-09-24 19:17 ` [PATCH 20/24] rtc: " matt mooney
2010-09-25  1:37   ` [rtc-linux] " Wan ZongShun
2010-09-24 19:17 ` [PATCH 21/24] scsi: " matt mooney
2010-09-24 19:17 ` [PATCH 22/24] spi: " matt mooney
2010-10-08 18:33   ` Grant Likely
2010-09-24 19:17 ` [PATCH 23/24] usb: " matt mooney
2010-09-24 20:02   ` [usb-storage] " Matthew Dharm
2010-09-24 20:28     ` matt mooney
2010-09-24 23:21       ` matt mooney
2010-09-24 19:17 ` [PATCH 24/24] video: " matt mooney
2010-09-25  2:52 ` [PATCH 01/24] base: " Américo Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100929155609.00a70ee0@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=ben-linux@fluff.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfm@muteddisk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox