On Thu, Nov 11, 2021 at 07:39:16AM -0800, Srivatsa S. Bhat wrote: > 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) <sriva...@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) <sriva...@csail.mit.edu> > > > Acked-by: Alexey Makhalov <amakha...@vmware.com> > > > Acked-by: Deep Shah <sd...@vmware.com> > > > Acked-by: Juergen Gross <jgr...@suse.com> > > > Cc: sta...@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 not how stable releases work at all. > 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. Patches for stable kernels need to go into Linus's tree first, and if you have the MAINTAINERS file updated properly there, then you will be properly cc:ed. We do not look at the MAINTAINERS file for the older kernel when sending patches out, it's totally ignored as that was the snapshot at a point in time, which is usually no longer the true state. So this would have no affect at all, sorry. That's why I asked if you all really realized what you were doing here :) thanks, greg k-h _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization
