mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.12-rc1
Date: Fri, 26 Feb 2021 14:16:41 +0100	[thread overview]
Message-ID: <20210226131641.4309-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.12b-rc1-tag

xen: branch for v5.12-rc1

It contains:

- A small series for Xen event channels adding some sysfs nodes for
  per pv-device settings and statistics, and 2 fixes of theoretical
  problems.

- two minor fixes (one for an unlikely error path, one for a comment).

Thanks.

Juergen

 Documentation/ABI/testing/sysfs-devices-xenbus | 41 ++++++++++++++++
 drivers/xen/events/events_base.c               | 27 ++++++++++-
 drivers/xen/evtchn.c                           | 29 ++++++-----
 drivers/xen/xen-acpi-processor.c               |  3 +-
 drivers/xen/xen-front-pgdir-shbuf.c            | 11 ++++-
 drivers/xen/xenbus/xenbus_probe.c              | 66 ++++++++++++++++++++++++++
 include/xen/xenbus.h                           |  7 +++
 7 files changed, 168 insertions(+), 16 deletions(-)

Jan Beulich (1):
      xen-front-pgdir-shbuf: don't record wrong grant handle upon error

Juergen Gross (3):
      xen/events: add per-xenbus device event statistics and settings
      xen/evtchn: use smp barriers for user event ring
      xen/evtchn: use READ/WRITE_ONCE() for accessing ring indices

Kees Cook (1):
      xen: Replace lkml.org links with lore

             reply	other threads:[~2021-02-26 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 13:16 Juergen Gross [this message]
2021-02-26 18:32 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-02-16 12:40 Juergen Gross
2021-02-21 22:01 ` 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=20210226131641.4309-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®