All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: Joe Perches <joe@perches.com>
Cc: Sasha Levin <sashal@kernel.org>,
	jgross@suse.com, anishs@vmware.com, pv-drivers@vmware.com,
	Greg KH <gregkh@linuxfoundation.org>,
	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>,
	kuba@kernel.org
Subject: Re: [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface
Date: Tue, 16 Nov 2021 10:18:37 -0800	[thread overview]
Message-ID: <20211116181837.GA24696@csail.mit.edu> (raw)
In-Reply-To: <70cd970d6c39a5ea5e88cbf4b86031c22c5d10d4.camel@perches.com>

On Mon, Nov 15, 2021 at 08:33:40PM -0800, Joe Perches wrote:
> On Mon, 2021-11-15 at 14:39 -0800, Srivatsa S. Bhat wrote:
> > On Fri, Nov 12, 2021 at 12:16:53PM -0500, Sasha Levin wrote:
> > > Maybe we should just remove MAINTAINERS from stable trees to make it
> > > obvious.
> > 
> > I don't think we should go quite that far. Instead, perhaps we can
> > modify get_maintainer.pl (if needed) such that it prints out a warning
> > or reminder to consult the upstream MAINTAINERS file if the script is
> > invoked on an older stable kernel.
> 
> I don't see how that's feasible.
> 

Not that I'm pushing for this change, but isn't it straight-forward to
distinguish upstream and stable kernel releases based on their
versioning schemes? The SUBLEVEL in the Makefile is always 0 for
upstream, and positive for stable versions (ignoring ancient kernels
like v2.6.32, of course). Since stable kernels are behind mainline by
definition, anytime the get_maintainer.pl script is invoked on a
kernel with a positive SUBLEVEL value, we can print out the said
warning/reminder (if it is considered useful).

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

WARNING: multiple messages have this Message-ID (diff)
From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: Joe Perches <joe@perches.com>
Cc: Sasha Levin <sashal@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	jgross@suse.com, x86@kernel.org, pv-drivers@vmware.com,
	Alexey Makhalov <amakhalov@vmware.com>,
	Deep Shah <sdeep@vmware.com>,
	stable@vger.kernel.org,
	virtualization@lists.linux-foundation.org, keerthanak@vmware.com,
	srivatsab@vmware.com, anishs@vmware.com, vithampi@vmware.com,
	linux-kernel@vger.kernel.org, namit@vmware.com, kuba@kernel.org,
	rostedt@goodmis.org
Subject: Re: [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops and VMware hypervisor interface
Date: Tue, 16 Nov 2021 10:18:37 -0800	[thread overview]
Message-ID: <20211116181837.GA24696@csail.mit.edu> (raw)
In-Reply-To: <70cd970d6c39a5ea5e88cbf4b86031c22c5d10d4.camel@perches.com>

On Mon, Nov 15, 2021 at 08:33:40PM -0800, Joe Perches wrote:
> On Mon, 2021-11-15 at 14:39 -0800, Srivatsa S. Bhat wrote:
> > On Fri, Nov 12, 2021 at 12:16:53PM -0500, Sasha Levin wrote:
> > > Maybe we should just remove MAINTAINERS from stable trees to make it
> > > obvious.
> > 
> > I don't think we should go quite that far. Instead, perhaps we can
> > modify get_maintainer.pl (if needed) such that it prints out a warning
> > or reminder to consult the upstream MAINTAINERS file if the script is
> > invoked on an older stable kernel.
> 
> I don't see how that's feasible.
> 

Not that I'm pushing for this change, but isn't it straight-forward to
distinguish upstream and stable kernel releases based on their
versioning schemes? The SUBLEVEL in the Makefile is always 0 for
upstream, and positive for stable versions (ignoring ancient kernels
like v2.6.32, of course). Since stable kernels are behind mainline by
definition, anytime the get_maintainer.pl script is invoked on a
kernel with a positive SUBLEVEL value, we can print out the said
warning/reminder (if it is considered useful).

Regards,
Srivatsa

  reply	other threads:[~2021-11-16 18:15 UTC|newest]

Thread overview: 47+ 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:07 ` Srivatsa S. Bhat
2021-11-10 20:07 ` 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-10 20:08   ` Srivatsa S. Bhat
2021-11-11  6:50   ` Greg KH
2021-11-11  6:50     ` Greg KH
2021-11-11 13:57     ` Steven Rostedt
2021-11-11 13:57       ` Steven Rostedt
2021-11-11 15:39     ` Srivatsa S. Bhat
2021-11-11 15:39       ` Srivatsa S. Bhat
2021-11-11 18:45       ` Greg KH
2021-11-11 18:45         ` Greg KH
2021-11-11 19:40         ` Srivatsa S. Bhat
2021-11-11 19:40           ` Srivatsa S. Bhat
2021-11-12  6:55           ` Greg KH
2021-11-12  6:55             ` Greg KH
2021-11-12 17:31             ` Srivatsa S. Bhat
2021-11-12 17:31               ` Srivatsa S. Bhat
2021-11-12 17:16           ` Sasha Levin
2021-11-12 17:16             ` Sasha Levin
2021-11-15 22:39             ` Srivatsa S. Bhat
2021-11-15 22:39               ` Srivatsa S. Bhat
2021-11-16  4:33               ` Joe Perches
2021-11-16  4:33                 ` Joe Perches
2021-11-16 18:18                 ` Srivatsa S. Bhat [this message]
2021-11-16 18:18                   ` Srivatsa S. Bhat
2021-11-16 23:11                   ` Joe Perches
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:08   ` Srivatsa S. Bhat
2021-11-10 20:09 ` [PATCH v3 3/3] MAINTAINERS: Mark VMware mailing list entries as email aliases Srivatsa S. Bhat
2021-11-10 20:09   ` Srivatsa S. Bhat
2021-11-10 20:09   ` Srivatsa S. Bhat
2021-11-11  1:39   ` Jakub Kicinski
2021-11-11  1:39     ` Jakub Kicinski
2021-11-11  5:19     ` Joe Perches
2021-11-11  5:19       ` Joe Perches
2021-11-11  5:19       ` Joe Perches
2021-11-11 13:55       ` Jakub Kicinski
2021-11-12 17:50         ` Srivatsa S. Bhat
2021-11-12 17:50           ` Srivatsa S. Bhat
2021-11-12 17:50           ` Srivatsa S. Bhat
     [not found]         ` <20211112174458.GB11364@csail.mit.edu>
2021-11-12 17:52           ` Joe Perches
2021-11-11 13:46   ` Juergen Gross
2021-11-11 13:46     ` Juergen Gross
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=20211116181837.GA24696@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=sashal@kernel.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 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.