From: Kumar Gala <galak@kernel.crashing.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Anton Vorontsov <avorontsov@ru.mvista.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
LinuxPPC Linux-LINUXPPC <LINUXPPC@freescale.com>
Subject: Re: 2.6.30 -mm merge plans
Date: Wed, 25 Mar 2009 11:24:01 -0500 [thread overview]
Message-ID: <98251C63-0A58-4C8A-B442-48A08CF318BC@kernel.crashing.org> (raw)
In-Reply-To: <20090323224615.cd29edfd.akpm@linux-foundation.org>
On Mar 24, 2009, at 12:46 AM, Andrew Morton wrote:
> Merge
>
> spi_mpc83xx-fix-sparse-warnings.patch
> spi_mpc83xx-rework-chip-selects-handling.patch
> spi_mpc83xx-add-of-platform-driver-bindings.patch
> powerpc-add-mmc-spi-slot-bindings.patch
> powerpc-83xx-add-mmc-spi-support-via-the-device-tree-for-mpc8323e-
> rdb.patch
> powerpc-fsl_soc-isolate-legacy-fsl_spi-support-to-mpc832x_rdb-
> boards.patch
Andrew,
I can pick these up via the powerpc.git tree since they are for a PPC
specific SPI driver. I intended to pick the last three patches once
the first three went in on the driver side. But I can deal with all 6
if you want me to.
- k
next prev parent reply other threads:[~2009-03-25 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 5:46 Andrew Morton
2009-03-24 7:57 ` [BUGFIX][PATCH(resend) mmotm] memcg: try_get_mem_cgroup_from_swapcache fix (Re: 2.6.30 -mm merge plans) Daisuke Nishimura
2009-03-24 21:48 ` one more tty reference leak [Was: 2.6.30 -mm merge plans] Jiri Slaby
2009-03-24 22:01 ` Jiri Slaby
2009-03-25 1:26 ` sd-async-shutdown.patch [was: " Robert Hancock
2009-03-25 1:29 ` Shaohua Li
2009-03-25 16:24 ` Kumar Gala [this message]
2009-03-25 17:14 ` 2.6.30 -mm merge plans Coly Li
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=98251C63-0A58-4C8A-B442-48A08CF318BC@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=LINUXPPC@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=avorontsov@ru.mvista.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®