[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fa686aa40912082215l30f0b843ve891d27648c24526@mail.gmail.com>
Date: Tue, 8 Dec 2009 23:15:12 -0700
From: Grant Likely <grant.likely@...retlab.ca>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: David Brownell <dbrownell@...rs.sourceforge.net>,
Sascha Hauer <s.hauer@...gutronix.de>,
linux-kernel@...r.kernel.org, Daniel Mack <daniel@...aq.de>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
spi-devel-general@...ts.sourceforge.net,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/5] spi-imx: some updates
On Tue, Dec 8, 2009 at 5:35 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> 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 ;)
Hmmm... maybe I'll be more selective then.
I've also got JH to set up a patchwork page for SPI so that I won't
drop anything on the floor. I could certainly use some help with
triaging & acking the stuff in there. Anyone want to volunteer?
>> 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.
Okay, thanks.
> Often there are stragglers who I need to route around. It's usually
> not a significant problem though.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/
Powered by blists - more mailing lists