From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
rdunlap@xenotime.net, imammedo@redhat.com, linux@eikelenboom.it,
mingo@elte.hu
Subject: [GIT PULL] (xen) stable/bug.fixes for 3.1-rc0 (or rc1)
Date: Sat, 6 Aug 2011 11:13:22 -0400 [thread overview]
Message-ID: <20110806151321.GA21552@dumpdata.com> (raw)
Hey Linus,
Please pull
git pull git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/bug.fixes
which is based off this 3.0 post commit b993fdbc7fe26f96b59003a3552c418a71aa0a9f
Linus Torvalds (1)
Merge branch 'upstream/xen-tracing2' of git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen
The reason for picking that specific branch is that two of that patches directly
fix the xen-tracing code. Another way might be to base the patches on 'upstream/xen-tracing2' tree,
but I didn't have that locally - Jeremy pushed that to you - hence this. If you would prefer
that Jeremy push the two fixes for xen-tracing2 from his tree we can definitly arrange that.
Back to the description: Couple of fixes for various combinations of CONFIG_, cleanup
patches from Igor to make initial bootup reporting easier to grok, and removing some
compile warnings.
Huang Weiyi (1):
xen/pciback: remove duplicated #include
Igor Mammedov (2):
xen: Fix printk() format in xen/setup.c
xen: Fix misleading WARN message at xen_release_chunk
Jeremy Fitzhardinge (1):
xen/tracing: it looks like we wanted CONFIG_FTRACE
Konrad Rzeszutek Wilk (4):
xen/grant: Fix compile warning.
xen/balloon: Fix compile errors - missing header files.
xen/self-balloon: Add dependency on tmem.
xen/trace: Fix compile error when CONFIG_XEN_PRIVILEGED_GUEST is not set
arch/x86/xen/Makefile | 2 +-
arch/x86/xen/setup.c | 10 ++++------
arch/x86/xen/trace.c | 1 +
drivers/xen/Kconfig | 2 +-
drivers/xen/grant-table.c | 2 +-
drivers/xen/xen-pciback/xenbus.c | 1 -
drivers/xen/xen-selfballoon.c | 4 ++--
7 files changed, 10 insertions(+), 12 deletions(-)
reply other threads:[~2011-08-06 15:13 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=20110806151321.GA21552@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=imammedo@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.