From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: [GIT PULL] (xen) stable/for-linus-3.10-rc5-tag
Date: Mon, 10 Jun 2013 12:53:20 -0400 [thread overview]
Message-ID: <20130610165320.GA6135@phenom.dumpdata.com> (raw)
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.10-rc5-tag
which has two fixes for regressions that occured in v3.10. The signed
tag has more details so replicating it here:
<tag>
Bug-fixes for regressions:
- xen/tmem stopped working after a certain combination of modprobe/swapon was used
- cpu online/offlining would trigger WARN_ON.
</tag>
Thanks!
arch/x86/xen/smp.c | 8 ++++++++
drivers/xen/tmem.c | 4 ++--
2 files changed, 10 insertions(+), 2 deletions(-)
Konrad Rzeszutek Wilk (2):
xen/smp: Fixup NOHZ per cpu data when onlining an offline CPU.
xen/tmem: Don't over-write tmem_frontswap_poolid after tmem_frontswap_init set it.
reply other threads:[~2013-06-10 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130610165320.GA6135@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xensource.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).