linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: dbrownell@users.sourceforge.net,
	spi-devel-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Michal Simek <michal.simek@petalogix.com>
Subject: Re: [RFC] two new linux-next trees (SPI and devicetree)
Date: Tue, 24 Nov 2009 18:11:39 -0800	[thread overview]
Message-ID: <20091124181139.b9e218ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <fa686aa40911241753lca699c9sa9ca0a0585a9d39d@mail.gmail.com>

On Tue, 24 Nov 2009 18:53:21 -0700 Grant Likely <grant.likely@secretlab.ca> wrote:

> > My current stash:
> >
> >
> > atmel_spi-fix-dma-addr-calculation-for-len-buffer_size.patch
> > spi-controller-driver-for-designware-spi-core.patch
> > spi-add-pci-interface-driver-for-designware-spi-core.patch
> > spi-add-pci-interface-driver-for-designware-spi-core-fix.patch
> > spi-controller-driver-for-designware-spi-core-fix.patch
> > spidev-add-proper-section-markers.patch
> > spidev-use-declare_bitmap-instead-of-declaring-the-array.patch
> > spidev-use-declare_bitmap-instead-of-declaring-the-array-checkpatch-fixes.patch
> > spi-drain-mxc-spi-transfer-buffer-when-probing-device.patch
> > spi_s3c24xx-add-fiq-pseudo-dma-support.patch
> 
> Since they're already in your tree, do you mind continuing to shepherd
> these (either merge or drop)?

Sure.

> > I haven't heard anything from David in over a month.
> 
> Okay, shall I go ahead and merge my change to MAINTAINERS through my
> tree too then?

OK by me.

  reply	other threads:[~2009-11-25  2:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25  0:54 [RFC] two new linux-next trees (SPI and devicetree) Grant Likely
2009-11-25  1:04 ` Andrew Morton
2009-11-25  1:53   ` Grant Likely
2009-11-25  2:11     ` Andrew Morton [this message]
2009-11-25  2:38 ` Stephen Rothwell

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=20091124181139.b9e218ed.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@petalogix.com \
    --cc=sfr@canb.auug.org.au \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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).