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.10-rc1c
Date: Sun, 25 Oct 2020 11:41:41 +0100 [thread overview]
Message-ID: <20201025104141.4698-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.10b-rc1c-tag
xen: branch for v5.10-rc1c
It contains:
- a series for the Xen pv block drivers adding module parameters for
better control of resource usge
- a cleanup series for the Xen event driver
Thanks.
Juergen
Documentation/ABI/testing/sysfs-driver-xen-blkback | 9 +++
.../ABI/testing/sysfs-driver-xen-blkfront | 11 ++-
Documentation/admin-guide/kernel-parameters.txt | 7 ++
arch/x86/xen/smp.c | 19 +++--
arch/x86/xen/xen-ops.h | 2 +
drivers/block/xen-blkback/xenbus.c | 22 +++--
drivers/block/xen-blkfront.c | 20 +++--
drivers/xen/events/events_2l.c | 7 +-
drivers/xen/events/events_base.c | 94 +++++++++++++++-------
drivers/xen/events/events_fifo.c | 9 ++-
drivers/xen/events/events_internal.h | 70 +++-------------
include/xen/events.h | 8 --
12 files changed, 152 insertions(+), 126 deletions(-)
Juergen Gross (5):
xen: remove no longer used functions
xen/events: make struct irq_info private to events_base.c
xen/events: only register debug interrupt for 2-level events
xen/events: unmask a fifo event channel only if it was masked
Documentation: add xen.fifo_events kernel parameter description
SeongJae Park (3):
xen-blkback: add a parameter for disabling of persistent grants
xen-blkfront: add a parameter for disabling of persistent grants
xen-blkfront: Apply changed parameter name to the document
next reply other threads:[~2020-10-25 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 10:41 Juergen Gross [this message]
2020-10-25 18:35 ` 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=20201025104141.4698-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®