From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: [PATCH] Fixes for v3.6 (v1).
Date: Thu, 16 Aug 2012 11:50:12 -0400 [thread overview]
Message-ID: <1345132214-15298-1-git-send-email-konrad.wilk@oracle.com> (raw)
I sent a git pull two days ago to Linus and then I realized yesterday
we still have two more bugs that should be fixed.
So these are two tiny fixes that I am going to propose for v3.6.
next reply other threads:[~2012-08-16 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 15:50 Konrad Rzeszutek Wilk [this message]
2012-08-16 15:50 ` [PATCH 1/2] xen/p2m: Fix for 32-bit builds the "Reserve 8MB of _brk space for P2M" Konrad Rzeszutek Wilk
2012-08-16 17:32 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-08-16 21:02 ` Konrad Rzeszutek Wilk
2012-08-17 11:14 ` David Vrabel
2012-08-17 13:06 ` Konrad Rzeszutek Wilk
2012-08-17 13:28 ` David Vrabel
2012-08-17 17:36 ` Konrad Rzeszutek Wilk
2012-08-16 15:50 ` [PATCH 2/2] Revert "xen PVonHVM: move shared_info to MMIO before kexec" Konrad Rzeszutek Wilk
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=1345132214-15298-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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).