From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Venkatesh Pallipadi <venki@google.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Mike Travis <travis@sgi.com>,
"Paul E. McKenney" <paul.mckenney@linaro.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Gilad Ben-Yossef <gilad@benyossef.com>
Subject: Re: [PATCH v2] arch/ia64: remove references to cpu_*_map.
Date: Mon, 20 Feb 2012 09:14:47 +1030 [thread overview]
Message-ID: <87sji68mu8.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20120215183204.7928884a.akpm@linux-foundation.org>
On Wed, 15 Feb 2012 18:32:04 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:
> This stuff probably isn't all in linux-next yet. I tried to get an
> update going today but failed. I'll try again tomorrow, but it depends
> on how many additional oopses and build breakages our team of top-notch
> engineers chooses to add overnight.
Ah. OK, please apply as many as you can; except for the ia64 stuff,
they're cleanup. After next merge window I'll do another sweep to catch
any dregs.
Thanks,
Rusty.
prev parent reply other threads:[~2012-02-19 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 10:53 [PATCH v2] arch/ia64: remove references to cpu_*_map Srivatsa S. Bhat
2012-02-15 21:02 ` Andrew Morton
2012-02-15 23:10 ` Rusty Russell
2012-02-16 1:58 ` Venki Pallipadi
2012-02-16 2:32 ` Andrew Morton
2012-02-19 22:44 ` Rusty Russell [this message]
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=87sji68mu8.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=gilad@benyossef.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paul.mckenney@linaro.org \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tony.luck@intel.com \
--cc=travis@sgi.com \
--cc=venki@google.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