virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Juergen Gross <jgross@suse.com>, X86 ML <x86@kernel.org>,
	Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	IngoMolnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: Which tree for paravirt related patches?
Date: Thu, 04 Nov 2021 10:18:24 +0100	[thread overview]
Message-ID: <87zgqk46u7.ffs@tglx> (raw)
In-Reply-To: <874k8s5lgz.ffs@tglx>

On Thu, Nov 04 2021 at 10:17, Thomas Gleixner wrote:

CC+ x86, peterz

> Juergen,
>
> On Thu, Nov 04 2021 at 06:53, Juergen Gross wrote:
>
>> 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.
>
> Sure.
>
>> 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.
>
> Fair enough.
>
>> 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.
>
> Will do.
>
> Thanks,
>
>         Thomas
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2021-11-04  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  5:53 Which tree for paravirt related patches? Juergen Gross via Virtualization
2021-11-04  9:17 ` Thomas Gleixner
2021-11-04  9:18   ` Thomas Gleixner [this message]
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=87zgqk46u7.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=JBeulich@suse.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jgross@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=virtualization@lists.linux-foundation.org \
    --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).