[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70cd970d6c39a5ea5e88cbf4b86031c22c5d10d4.camel@perches.com>
Date: Mon, 15 Nov 2021 20:33:40 -0800
From: Joe Perches <joe@...ches.com>
To: "Srivatsa S. Bhat" <srivatsa@...il.mit.edu>,
Sasha Levin <sashal@...nel.org>
Cc: Greg KH <gregkh@...uxfoundation.org>, jgross@...e.com,
x86@...nel.org, pv-drivers@...are.com,
Alexey Makhalov <amakhalov@...are.com>,
Deep Shah <sdeep@...are.com>, stable@...r.kernel.org,
virtualization@...ts.linux-foundation.org, keerthanak@...are.com,
srivatsab@...are.com, anishs@...are.com, vithampi@...are.com,
linux-kernel@...r.kernel.org, namit@...are.com, kuba@...nel.org,
rostedt@...dmis.org
Subject: Re: [PATCH v3 1/3] MAINTAINERS: Update maintainers for paravirt ops
and VMware hypervisor interface
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.
Powered by blists - more mailing lists