xen-devel.lists.xenproject.org archive mirror
 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.11-rc1
Date: Sat, 19 Dec 2020 07:31:36 +0100	[thread overview]
Message-ID: <20201219063136.5828-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.11-rc1b-tag

xen: branch for v5.11-rc1

It contains some minor cleanup patches and a small series disentangling some Xen
related Kconfig options.

Thanks.

Juergen

 arch/x86/include/asm/xen/page.h |  2 +-
 arch/x86/xen/Kconfig            | 38 ++++++++++++++++++++++----------------
 arch/x86/xen/p2m.c              | 12 +-----------
 drivers/block/xen-blkfront.c    |  1 +
 drivers/xen/Makefile            |  2 +-
 drivers/xen/manage.c            |  1 +
 6 files changed, 27 insertions(+), 29 deletions(-)

Gustavo A. R. Silva (2):
      xen-blkfront: Fix fall-through warnings for Clang
      xen/manage: Fix fall-through warnings for Clang

Jason Andryuk (3):
      xen: Remove Xen PVH/PVHVM dependency on PCI
      xen: Kconfig: nest Xen guest options
      xen: Kconfig: remove X86_64 depends from XEN_512GB

Qinglang Miao (1):
      x86/xen: Convert to DEFINE_SHOW_ATTRIBUTE

Tom Rix (1):
      xen: remove trailing semicolon in macro definition


             reply	other threads:[~2020-12-19  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19  6:31 Juergen Gross [this message]
2020-12-19 21:06 ` [GIT PULL] xen: branch for v5.11-rc1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-12-15 12:26 Juergen Gross
2020-12-16 20:16 ` 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=20201219063136.5828-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;
as well as URLs for NNTP newsgroup(s).