From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jgross@suse.com, anishs@vmware.com, pv-drivers@vmware.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
virtualization@lists.linux-foundation.org, keerthanak@vmware.com,
namit@vmware.com, rostedt@goodmis.org,
Alexey Makhalov <amakhalov@vmware.com>,
joe@perches.com, kuba@kernel.org
Subject: Re: [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface
Date: Thu, 11 Nov 2021 07:39:16 -0800 [thread overview]
Message-ID: <20211111153916.GA7966@csail.mit.edu> (raw)
In-Reply-To: <YYy9P7Rjg9hntmm3@kroah.com>
On Thu, Nov 11, 2021 at 07:50:39AM +0100, Greg KH wrote:
> On Wed, Nov 10, 2021 at 12:08:16PM -0800, Srivatsa S. Bhat wrote:
> > From: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> >
> > Deep has decided to transfer maintainership of the VMware hypervisor
> > interface to Srivatsa, and the joint-maintainership of paravirt ops in
> > the Linux kernel to Srivatsa and Alexey. Update the MAINTAINERS file
> > to reflect this change.
> >
> > Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> > Acked-by: Alexey Makhalov <amakhalov@vmware.com>
> > Acked-by: Deep Shah <sdeep@vmware.com>
> > Acked-by: Juergen Gross <jgross@suse.com>
> > Cc: stable@vger.kernel.org
>
> Why are MAINTAINERS updates needed for stable? That's not normal :(
So that people posting bug-fixes / backports to these subsystems for
older kernels (stable and LTS releases) will CC the new subsystem
maintainers. That's why I added CC stable tag only to the first two
patches which add/replace maintainers and not the third patch which is
just a cleanup.
Regards,
Srivatsa
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-11-11 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:07 [PATCH v3 0/3] Update VMware maintainer entries Srivatsa S. Bhat
2021-11-10 20:08 ` [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface Srivatsa S. Bhat
2021-11-11 6:50 ` Greg KH
2021-11-11 13:57 ` Steven Rostedt
2021-11-11 15:39 ` Srivatsa S. Bhat [this message]
2021-11-11 18:45 ` Greg KH
2021-11-11 19:40 ` Srivatsa S. Bhat
2021-11-12 6:55 ` Greg KH
2021-11-12 17:31 ` Srivatsa S. Bhat
2021-11-12 17:16 ` Sasha Levin
2021-11-15 22:39 ` Srivatsa S. Bhat
2021-11-16 4:33 ` Joe Perches
2021-11-16 18:18 ` Srivatsa S. Bhat
2021-11-16 23:11 ` Joe Perches
2021-11-10 20:08 ` [PATCH v3 2/3] MAINTAINERS: Add Zack as maintainer of vmmouse driver Srivatsa S. Bhat
2021-11-10 20:09 ` [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases Srivatsa S. Bhat
[not found] ` <20211110173935.45a9f495@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-11-11 5:19 ` Joe Perches
[not found] ` <20211111055554.4f257fd2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2021-11-12 17:50 ` Srivatsa S. Bhat
2021-11-11 13:46 ` Juergen Gross via Virtualization
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=20211111153916.GA7966@csail.mit.edu \
--to=srivatsa@csail.mit.edu \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=joe@perches.com \
--cc=keerthanak@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@vmware.com \
--cc=pv-drivers@vmware.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.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).