linux-kernel - Re: [PATCH 05/24] i2c: change to new flag variable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Sep 2010 15:56:09 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	matt mooney <mfm@...eddisk.com>
Cc:	kernel-janitors@...r.kernel.org,
	"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH 05/24] i2c: change to new flag variable

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/