All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
	Juergen Gross <jgross@suse.com>, X86 ML <x86@kernel.org>,
	Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Pv-drivers <Pv-drivers@vmware.com>, IngoMolnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>, Jan Beulich <JBeulich@suse.com>,
	amakhalov@vmware.com
Subject: Re: Which tree for paravirt related patches?
Date: Thu, 04 Nov 2021 21:11:51 +0100	[thread overview]
Message-ID: <87o86z4r5k.ffs@tglx> (raw)
In-Reply-To: <b4288d2d-8300-6d1f-f4d1-8d922f46fb70@csail.mit.edu>

Srivatsa,

On Thu, Nov 04 2021 at 12:09, Srivatsa S. Bhat wrote:
> On a related note, I'll be stepping in soon to assist (in place of
> Deep) as a co-maintainer of the PARAVIRT_OPS interface. I had the same
> query about which tree would be best for patches to the paravirt-ops
> code, so I'm glad to see that it got clarified on this thread.

Welcome to the club.

> I'll also be taking over the maintainership of the VMware hypervisor
> interface. Looking at the git logs, I believe those patches have
> also been handled via the tip tree; so would it be okay to add the
> x86 ML and the tip tree to the VMware hypervisor interface entry too
> in the MAINTAINERS file?

We've routed them through tip, yes. So yes, that's fine to have a
separate entry in the maintainers file which has you and x86@kernel.org
plus the tip tree mentioned.

Thanks,

        tglx


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

  reply	other threads:[~2021-11-04 20:12 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
2021-11-04 19:09     ` Srivatsa S. Bhat
2021-11-04 20:11       ` Thomas Gleixner [this message]
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=87o86z4r5k.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=JBeulich@suse.com \
    --cc=Pv-drivers@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jgross@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=srivatsa@csail.mit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.