From: Andrew Morton on
On Tue, 24 Nov 2009 17:54:27 -0700
Grant Likely <grant.likely(a)secretlab.ca> wrote:

> I've made the offer to be SPI
> co-maintainer,

OK by me. Don't break anything.

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


> but I haven't received any feedback yet from either
> akpm or dbrownell.

I haven't heard anything from David in over a month.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Grant Likely on
On Tue, Nov 24, 2009 at 6:04 PM, Andrew Morton
<akpm(a)linux-foundation.org> wrote:
> On Tue, 24 Nov 2009 17:54:27 -0700
> Grant Likely <grant.likely(a)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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on
On Tue, 24 Nov 2009 18:53:21 -0700 Grant Likely <grant.likely(a)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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Rothwell on
Hi Grant,

On Tue, 24 Nov 2009 17:54:27 -0700 Grant Likely <grant.likely(a)secretlab.ca> wrote:
>
> First one is a bunch of SPI patches. I've made the offer to be SPI
> co-maintainer, but I haven't received any feedback yet from either
> akpm or dbrownell. In the mean time, I still have a bunch of SPI
> patches (properly signed off and everything) that should have
> linux-next exposure before the merge window. I've put them in the
> tree shown in the request-pull output below.
>
> David, akpm, please note: I'm not intending to ask Linus to pull this
> tree, but I do really need some feedback on what you want me to do.
> The tree should be properly formed and signed off, so I can ask Linus
> to pull from me directly if you wish.
>
> git://git.secretlab.ca/git/linux-2.6 next-spi

I have added this to linux-next from today.

Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.

--
Cheers,
Stephen Rothwell
sfr(a)canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.