virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross via Virtualization <virtualization@lists.linux-foundation.org>
To: X86 ML <x86@kernel.org>,
	Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	IngoMolnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Jan Beulich <JBeulich@suse.com>
Subject: Which tree for paravirt related patches?
Date: Thu, 4 Nov 2021 06:53:29 +0100	[thread overview]
Message-ID: <60a2037d-2d4d-e9e9-edfd-b889c4bd3fb6@suse.com> (raw)


[-- Attachment #1.1.1.1: Type: text/plain, Size: 904 bytes --]

A recent patch modifying the core paravirt-ops functionality is
highlighting some missing MAINTAINERS information for PARAVIRT_OPS:
there is no information which tree is to be used for taking those
patches per default. In the past this was mostly handled by the tip
tree, and I think this is fine.

X86 maintainers, are you fine with me modifying the PARAVIRT_OPS entry
to add the x86 ML and the tip tree? This way such patches will be
noticed by you and can be handled accordingly.

An alternative would be to let me carry those patches through the Xen
tree, but in lots of those patches some core x86 files are being touched
and I think the tip tree is better suited for paravirt handling.

And please, could you take a look at:

https://lore.kernel.org/virtualization/b8192e8a-13ef-6ac6-6364-8ba58992cd1d@suse.com/

This patch was the one making me notice the problem.


Juergen

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

             reply	other threads:[~2021-11-04  5:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  5:53 Juergen Gross via Virtualization [this message]
2021-11-04  9:17 ` Which tree for paravirt related patches? Thomas Gleixner
2021-11-04  9:18   ` Thomas Gleixner
2021-11-04 19:09     ` Srivatsa S. Bhat
2021-11-04 20:11       ` Thomas Gleixner
2021-11-04 20:17         ` Srivatsa S. Bhat

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=60a2037d-2d4d-e9e9-edfd-b889c4bd3fb6@suse.com \
    --to=virtualization@lists.linux-foundation.org \
    --cc=JBeulich@suse.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jgross@suse.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).