xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: [PATCH v1] Bug-fixes for v3.7 back-ported from Jan's postings.
Date: Mon, 29 Oct 2012 10:08:16 -0400	[thread overview]
Message-ID: <1351519698-11069-1-git-send-email-konrad.wilk@oracle.com> (raw)

These are back-ports from the ones that Jan posted. Please
take a look  - I might have missed an email about one of the patches
and I can't find it my mailbox :-(

Either way, was thinking to put these in v3.7.

 arch/x86/include/asm/xen/hypercall.h     |   21 +++-----
 drivers/xen/Makefile                     |    2 +-
 drivers/xen/fallback.c                   |   78 ++++++++++++++++++++++++++++++
 drivers/xen/xenbus/xenbus_dev_frontend.c |    2 +-
 4 files changed, 87 insertions(+), 16 deletions(-)


Jan Beulich (2):
      xen/hypercall: fix hypercall fallback code for very old hypervisors
      xen/xenbus: fix overflow check in xenbus_file_write()

             reply	other threads:[~2012-10-29 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 14:08 Konrad Rzeszutek Wilk [this message]
2012-10-29 14:08 ` [PATCH 1/2] xen/hypercall: fix hypercall fallback code for very old hypervisors Konrad Rzeszutek Wilk
2012-10-30 15:44   ` Konrad Rzeszutek Wilk
2012-10-31  8:55     ` Jan Beulich
     [not found]     ` <5090F5AA02000078000A5A0B@nat28.tlf.novell.com>
2012-11-02 16:44       ` Konrad Rzeszutek Wilk
     [not found]       ` <20121102164409.GB27213@konrad-lan.dumpdata.com>
2012-11-02 16:57         ` Jan Beulich
2012-10-29 14:08 ` [PATCH 2/2] xen/xenbus: fix overflow check in xenbus_file_write() 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=1351519698-11069-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).