linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <dvrabel@cantab.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: [GIT PULL] xen: bug fixes for 4.5-rc5
Date: Mon, 22 Feb 2016 13:18:45 +0000	[thread overview]
Message-ID: <56CB0AB5.4030400@cantab.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Linus,

Please git pull the following tag:

 git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.5-rc5-tag

Xen bug fixes for 4.5-rc5

- - Two scsiback fixes (resource leak and spurious warning).
- - Fix DMA mapping of compound pages on arm/arm64.
- - Fix some pciback regressions in MSI-X handling.
- - Fix a pcifront crash due to some uninitialize state.

Thanks.

David

 arch/arm/include/asm/xen/page-coherent.h | 21 ++++++---
 arch/x86/include/asm/xen/pci.h           |  4 +-
 arch/x86/pci/xen.c                       |  5 +-
 drivers/pci/xen-pcifront.c               | 10 ++--
 drivers/xen/xen-pciback/pciback_ops.c    |  9 +++-
 drivers/xen/xen-scsiback.c               | 80 ++++++++++++++++++--------------
 drivers/xen/xenbus/xenbus_dev_frontend.c |  2 +
 7 files changed, 81 insertions(+), 50 deletions(-)

Ian Campbell (1):
      xen/arm: correctly handle DMA mapping of compound pages

Insu Yun (1):
      xen: fix potential integer overflow in queue_reply

Juergen Gross (2):
      xen/scsiback: correct frontend counting
      xen/scsiback: avoid warnings when adding multiple LUNs to a domain

Konrad Rzeszutek Wilk (4):
      xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY
      xen/pciback: Save the number of MSI-X entries to be copied later.
      xen/pcifront: Report the errors better.
      xen/pcifront: Fix mysterious crashes when NUMA locality information was extracted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWywq1AAoJEFxbo/MsZsTRdp0H/iq2sxOtCSXqytfV/XOau7As
HCA7tHYkY/MEZ01I2uIajXfOoKrFRcSBoU3jCEYBbnu7gv5/jEwiGFDxgM4dw5bK
eywUK5TF9il9byq1Ys/WJkuIYoeBC+VV8c7niStnEgr2R9TNMp66U6IMqPhqmCnK
+6a3npuzJ+RckyNF3fMJOrgzuIqashUZ6ghdawRVcT+BKg6rAGriYIPHB22ek1fR
K+dszjt6xKKT42nhHggWkINmV9Gmi23E7HrwuAqq+UiYMmBImJlwLnWMx9yLhh+r
0xpRdJKU4zaUAIOqNlVY6QwRfRY+Yvdh0HDoTog2Y4lDysT4fl0DGiHlpJRFaho=
=vyvq
-----END PGP SIGNATURE-----

                 reply	other threads:[~2016-02-22 13:19 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=56CB0AB5.4030400@cantab.net \
    --to=dvrabel@cantab.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).