From: Juergen Gross <jgross@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
boris.ostrovsky@oracle.com
Subject: [GIT PULL] xen: branch for v5.7-rc1
Date: Fri, 10 Apr 2020 08:24:30 +0200 [thread overview]
Message-ID: <20200410062430.20949-1-jgross@suse.com> (raw)
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.7-rc1b-tag
xen: branch for v5.7-rc1b
This is a second batch of Xen related patches:
- two cleanup patches
- a patch to fix a boot regression introduced earlier in 5.7
- a patch to fix wrong usage of memory allocation flags
Thanks.
Juergen
arch/x86/xen/setup.c | 2 +-
arch/x86/xen/xen-head.S | 2 +-
drivers/block/xen-blkfront.c | 17 +++++--
drivers/xen/events/events_2l.c | 16 +++---
drivers/xen/events/events_base.c | 93 ++++++++++++++++++-----------------
drivers/xen/events/events_fifo.c | 22 ++++-----
drivers/xen/events/events_internal.h | 30 +++++------
drivers/xen/evtchn.c | 13 ++---
drivers/xen/gntdev-common.h | 3 +-
drivers/xen/gntdev.c | 2 +-
drivers/xen/pvcalls-back.c | 5 +-
drivers/xen/pvcalls-front.c | 15 +++---
drivers/xen/xen-pciback/xenbus.c | 7 +--
drivers/xen/xen-scsiback.c | 3 +-
drivers/xen/xenbus/xenbus_client.c | 6 +--
include/xen/events.h | 22 ++++-----
include/xen/interface/event_channel.h | 2 +-
include/xen/xenbus.h | 5 +-
18 files changed, 142 insertions(+), 123 deletions(-)
Jason Yan (1):
x86/xen: make xen_pvmmu_arch_setup() static
Juergen Gross (2):
xen/blkfront: fix memory allocation flags in blkfront_setup_indirect()
x86/xen: fix booting 32-bit pv guest
Yan Yankovskyi (1):
xen: Use evtchn_type_t as a type for event channels
next reply other threads:[~2020-04-10 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 6:24 Juergen Gross [this message]
2020-04-11 1:20 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-04-03 15:54 Juergen Gross
2020-04-03 20:50 ` pr-tracker-bot
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=20200410062430.20949-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--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
all inboxes | Powered by JetHome®