From: Andrew Morton <akpm@linux-foundation.org>
To: Cong Wang <amwang@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Greg KH <greg@kroah.com>
Subject: Re: linux-next: manual merge of the kmap_atomic tree with the staging.current tree
Date: Thu, 9 Feb 2012 00:45:59 -0800 [thread overview]
Message-ID: <20120209004559.322475d0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1328776797.20628.18.camel@cr0>
On Thu, 09 Feb 2012 16:39:57 +0800 Cong Wang <amwang@redhat.com> wrote:
> As Linus doesn't want to merge my tree, could any of you take my patches
> in kmap_atomic tree?
He's not the messiah, he's a very naughty boy.
Send 'em over.
next prev parent reply other threads:[~2012-02-09 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 3:48 linux-next: manual merge of the kmap_atomic tree with the staging.current tree Stephen Rothwell
2012-02-09 8:39 ` Cong Wang
2012-02-09 8:45 ` Andrew Morton [this message]
2012-02-09 9:26 ` Cong Wang
-- strict thread matches above, loose matches on Subject: below --
2012-01-31 3:27 Stephen Rothwell
2012-01-31 3:39 ` Cong Wang
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=20120209004559.322475d0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sjenning@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).