From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: [GIT PULL] xen: xenbus driver fixes
Date: Thu, 20 Jan 2011 11:59:27 -0800 [thread overview]
Message-ID: <4D38941F.9070101@goop.org> (raw)
Hi Linus,
Here's a handful of little bugfixes for the xenbus driver which were
overlooked in the last merge window. They've been floating around in
linux-next and xen.git master for ages.
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/xenbus
Daniel De Graaf (3):
xenbus: add missing wakeup in concurrent read/write
xenbus: avoid zero returns from read()
xenbus: Fix memory leak on release
Diego Ongaro (1):
xenbus: allow any xenbus command over /proc/xen/xenbus
Jeremy Fitzhardinge (1):
xenfs/xenbus: report partial reads/writes correctly
drivers/xen/xenfs/xenbus.c | 31 +++++++++++++------------------
1 files changed, 13 insertions(+), 18 deletions(-)
Thanks,
J
reply other threads:[~2011-01-20 19:59 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=4D38941F.9070101@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome