From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] spi-imx: some updates
Date: Tue, 8 Dec 2009 16:35:46 -0800 [thread overview]
Message-ID: <20091208163546.3354a7f5.akpm@linux-foundation.org> (raw)
In-Reply-To: <fa686aa40912081625y3750a7fegbac38926182e38c6@mail.gmail.com>
On Tue, 8 Dec 2009 17:25:59 -0700
Grant Likely <grant.likely@secretlab.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.
next prev parent reply other threads:[~2009-12-09 0:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 21:12 [PATCH 0/5] spi-imx: some updates Uwe Kleine-König
2009-12-08 21:14 ` [PATCH 1/5] spi-imx: use platform_driver_probe as probe lives in .init.text Uwe Kleine-König
2009-12-08 21:14 ` [PATCH 2/5] spi-imx: correct check for platform_get_irq failing Uwe Kleine-König
2009-12-08 21:14 ` [PATCH 3/5] spi-imx: use positive logic to distinguish cpu variants Uwe Kleine-König
2009-12-08 21:14 ` [PATCH 4/5] spi-imx: Add mx25 support Uwe Kleine-König
2009-12-08 21:14 ` [PATCH 5/5] spi-imx: don't access struct device directly but use dev_get_platdata Uwe Kleine-König
2009-12-08 23:32 ` [PATCH 0/5] spi-imx: some updates Andrew Morton
2009-12-09 0:25 ` Grant Likely
2009-12-09 0:35 ` Andrew Morton [this message]
2009-12-09 6:15 ` Grant Likely
2009-12-09 0:47 ` [spi-devel-general] " jassi brar
2009-12-09 1:50 ` Grant Likely
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=20091208163546.3354a7f5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).