The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Andrew Morton <akpm@linux-foundation.org>
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:53:21 -0700	[thread overview]
Message-ID: <fa686aa40911241753lca699c9sa9ca0a0585a9d39d@mail.gmail.com> (raw)
In-Reply-To: <20091124170419.92cb63f6.akpm@linux-foundation.org>

On Tue, Nov 24, 2009 at 6:04 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 24 Nov 2009 17:54:27 -0700
> Grant Likely <grant.likely@secretlab.ca> wrote:
>
>> I've made the offer to be SPI
>> co-maintainer,
>
> OK by me.  Don't break anything.

I'll do my best.

> 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)?  I've gotten a patchwork project set up
on kernel.org for the spi mailing list, so I can easily track things
from this point on.  My gameplan at this point is to try and stay on
top of the things that I'm familiar with (mostly powerpc) and depend
on other people to ack the rest.  I'll pick up anything that a)
doesn't look ugly, b) isn't contested, and c) applies.  :-)

>> but I haven't received any feedback yet from either
>> akpm or dbrownell.
>
> 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?

g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-11-25  1:53 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 [this message]
2009-11-25  2:11     ` Andrew Morton
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=fa686aa40911241753lca699c9sa9ca0a0585a9d39d@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=dbrownell@users.sourceforge.net \
    --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