linux-kernel - Re: [PATCH 0/5] spi-imx: some updates

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]

Message-Id: <20091208163546.3354a7f5.akpm@linux-foundation.org>
Date:	Tue, 8 Dec 2009 16:35:46 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>,
	spi-devel-general@...ts.sourceforge.net,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	Sascha Hauer <s.hauer@...gutronix.de>,
	Daniel Mack <daniel@...aq.de>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] spi-imx: some updates

On Tue, 8 Dec 2009 17:25:59 -0700
Grant Likely <grant.likely@...retlab.ca> wrote:

> I'm new to the job, so I'm being cautions about which things I'm pick
> up.  However, I'll happily merge anything that Andrew says is okay.

oop.  If I'm going to send a patch to a subsystem maintainer I'll usually give
it less attention than the ones I plan to merge myself.

Oh well, at least this way people will get their patches merged easily ;)

> Andrew, when in the merge window do you typically send out patch
> queues?

Late.  I stage the -mm patches after linux-next so I spend most of the
merge window waiting for people to get their stuff into mainline.

Often there are stragglers who I need to route around.  It's usually
not a significant problem though.
--
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/