All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] (xen) stable/for-linus-3.4-rc3-tag
Date: Fri, 20 Apr 2012 12:17:46 -0400	[thread overview]
Message-ID: <20120420161746.GA28366@phenom.dumpdata.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

Hey Linus,

Please git pull the following tag for v3.4-rc4:

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.4-rc3-tag

which has a some compile warning fixes and mechanisms to work
around misbehaving backends. Also there is fix to the internal
mechanism for dealing with pages brought in from a guest (and
one fix that I had to revert last minute). Lastly a fix from Julia
to return proper error code.

Please pull!

Julia Lawall (1):
      xen/grant-table: add error-handling code on failure of gnttab_resume

Konrad Rzeszutek Wilk (4):
      xen/blkback: Fix warning error.
      xen/xenbus: Add quirk to deal with misconfigured backends.
      xen/resume: Fix compile warnings.
      Revert "xen/p2m: m2p_find_override: use list_for_each_entry_safe"

Stefano Stabellini (2):
      xen/gntdev: do not set VM_PFNMAP
      xen/p2m: m2p_find_override: use list_for_each_entry_safe

 drivers/block/xen-blkback/xenbus.c         |    2 +-
 drivers/xen/gntdev.c                       |    2 +-
 drivers/xen/grant-table.c                  |   13 ++++--
 drivers/xen/manage.c                       |    1 +
 drivers/xen/xenbus/xenbus_probe_frontend.c |   69 +++++++++++++++++++++------
 5 files changed, 65 insertions(+), 22 deletions(-)

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

                 reply	other threads:[~2012-04-20 16:22 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=20120420161746.GA28366@phenom.dumpdata.com \
    --to=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 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.