From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Seth Forshee <seth.forshee@canonical.com>,
Christoph Hellwig <hch@lst.de>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>
Subject: linux-next: fixes while rebasing the akpm tree
Date: Mon, 4 Jul 2011 16:28:16 +1000 [thread overview]
Message-ID: <20110704162816.fef0b1cb.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
Hi Andrew,
While rebasing the akpm tree onto today's linux-next, I discovered the
following:
The patch hfsplus-add-missing-call-to-bio_put.patch appears to be already
applied (as commit 50176ddefa4a ("hfsplus: add missing call to bio_put()"
from the hfsplus tree).
The patches
x86-mtrr-lock-stop-machine-during-mtrr-rendezvous-sequence.patch,
stop_machine-reorganize-stop_cpus-implementation.patch and
stop_machine-implement-stop_machine_from_inactive_cpu.patch seem to be
already applied (as commits 6d3321e8e2b3 ("x86, mtrr: lock stop machine
during MTRR rendezvous sequence"), fd7355ba1e93 ("stop_machine:
reorganize stop_cpus() implementation") and f740e6cd0cb5 ("stop_machine:
implement stop_machine_from_inactive_cpu()") from the tip tree)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-07-04 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 6:28 Stephen Rothwell [this message]
2011-07-05 6:31 ` 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=20110704162816.fef0b1cb.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=seth.forshee@canonical.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®