From: Andrew Morton <akpm@linux-foundation.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: mmotm 2010-06-03-16-36 uploaded
Date: Thu, 3 Jun 2010 18:34:10 -0700 [thread overview]
Message-ID: <20100603183410.bf61f113.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100604101329D.fujita.tomonori@lab.ntt.co.jp>
On Fri, 4 Jun 2010 10:14:27 +0900 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> On Thu, 03 Jun 2010 16:36:51 -0700
> akpm@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2010-06-03-16-36 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
> >
> > git://zen-kernel.org/kernel/mmotm.git
> >
> > It contains the following patches against 2.6.35-rc1:
>
> (snip)
>
> > ssb-add-dma_dev-to-ssb_device-structure.patch
> > b43legacy-replace-the-ssb_dma-api-with-the-generic-dma-api.patch
> > b43-replace-the-ssb_dma-api-with-the-generic-dma-api.patch
> > b44-replace-the-ssb_dma-api-with-the-generic-dma-api.patch
> > ssb-remove-the-ssb-dma-api.patch
>
> Is there any reason why the above patches are still in -mm (i.e. not
> merged in the previous merge window)?
Two lines earlier:
# propagate these:
is akpm shorthand for "send these through maintainers".
I prefer to go that way if the patch isn't urgent, just to get a bit
more attention and review. If the patch has a maintainer ack already
then I'll often merge it directly.
> I got an ACK on the first patch to ssb core from the ssb maintainer,
> ACKs on the second and third to b43legacy and b43 from the maintainer.
>
> http://marc.info/?t=126621151900002&r=1&w=2
And none of the above patches were sent to me with acked-by:s, and
nobody sent new acked-by:s, so I didn't know this!
I guess John is the conduit for all five of the above so I'll send them
to him now and he might decide to squeak them into 2.6.35.
But before I do that, please send me an email telling me who acked each
patch and I'll update that info.
Thanks.
next prev parent reply other threads:[~2010-06-04 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 23:36 akpm
2010-06-04 1:14 ` FUJITA Tomonori
2010-06-04 1:34 ` Andrew Morton [this message]
2010-06-04 2:16 ` FUJITA Tomonori
2010-06-04 9:32 ` Michael Büsch
2010-06-04 1:41 ` Dave Young
2010-06-04 1:54 ` Andrew Morton
2010-06-04 2:02 ` Dave Young
2010-06-04 2:10 ` Andrew Morton
2010-06-04 2:13 ` Dave Young
2010-06-04 1:56 ` Andrew Morton
2010-06-04 2:23 ` Valdis.Kletnieks
2010-06-04 16:41 ` [PATCH -mmotm] cciss: fix build for CONFIG_PROC_FS=n Randy Dunlap
2010-06-04 18:07 ` Miller, Mike (OS Dev)
2010-06-05 12:15 ` mmotm 2010-06-03-16-36 uploaded 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=20100603183410.bf61f113.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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
Powered by JetHome