From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
dedekind1@gmail.com, linux-kernel@vger.kernel.org,
dwmw2@infradead.org, kmpark@infradead.org,
linux-mtd@lists.infradead.org
Subject: Re: 2.6.32 -mm merge plans
Date: Tue, 15 Sep 2009 21:15:58 -0700 [thread overview]
Message-ID: <20090915211558.85a7825a.akpm@linux-foundation.org> (raw)
In-Reply-To: <8bd0f97a0909152051s4a25b9eej581c68a3b10fda3@mail.gmail.com>
On Tue, 15 Sep 2009 23:51:25 -0400 Mike Frysinger <vapier.adi@gmail.com> wrote:
> > I don't think that Artem's tree is in linux-next, so I have no
> > visibility of what's happening with that patch.
> >
> > I do think that Artem's tree should be in linux-next.
> >
> > I guess I'll just hose the patch at dwmw2 and will see what happens. __I
> > sent it on Aug 6, with no effect.
>
> i guess i shouldnt try and bounce a few more mtd patches through you huh ...
You can try. One of my functions is pointlessly sending patches at
maintainers so you don't have to.
> http://git.kernel.org/?p=linux/kernel/git/vapier/blackfin.git;a=shortlog;h=for-mtd
>
> hopefully they make it in this cycle (they were posted a while ago to
> the mtd lists w/feedback addressed)
Wanna mail them out in the usual fashion?
next prev parent reply other threads:[~2009-09-16 4:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 23:15 2.6.32 -mm merge plans Andrew Morton
2009-09-16 0:03 ` Paul Mundt
2009-09-16 0:18 ` Andrew Morton
2009-09-16 3:51 ` Mike Frysinger
2009-09-16 4:15 ` Andrew Morton [this message]
2009-09-16 4:17 ` Mike Frysinger
2009-09-16 7:21 ` Artem Bityutskiy
2009-09-16 7:09 ` Artem Bityutskiy
2009-09-16 7:36 ` Artem Bityutskiy
2009-09-16 3:46 ` Dmitry Torokhov
2009-09-16 4:14 ` Andrew Morton
2009-09-16 8:33 ` David Härdeman
2009-09-16 15:00 ` Bjorn Helgaas
2009-09-16 20:00 ` Andrew Morton
2009-09-16 7:37 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Balbir Singh
2009-09-16 7:51 ` Daisuke Nishimura
2009-09-16 7:58 ` KAMEZAWA Hiroyuki
2009-09-16 8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16 9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:38 ` Andrew Morton
2009-09-17 21:08 ` Oleg Nesterov
2009-09-17 20:32 ` do_wait() changes " Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 21:56 ` Roland McGrath
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=20090915211558.85a7825a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kmpark@infradead.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.com \
/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