[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023071004-engaged-garter-171c@gregkh>
Date: Mon, 10 Jul 2023 16:09:06 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Mark Brown <broonie@...nel.org>
Cc: Will Deacon <will@...nel.org>, Sasha Levin <sashal@...nel.org>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Kristina Martsenko <kristina.martsenko@....com>,
Catalin Marinas <catalin.marinas@....com>, james.morse@....com,
mark.rutland@....com, amit.kachhap@....com, maz@...nel.org,
anshuman.khandual@....com, joey.gouly@....com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH AUTOSEL 6.4 07/12] arm64: cpufeature: detect FEAT_HCX
On Mon, Jul 10, 2023 at 02:47:12PM +0100, Mark Brown wrote:
> On Mon, Jul 10, 2023 at 03:31:42PM +0200, Greg KH wrote:
> > On Mon, Jul 10, 2023 at 10:44:38AM +0100, Will Deacon wrote:
>
> > > Maybe we just need a commit hook that yells if something with a Fixes:
> > > tag doesn't have a CC: stable on it?
>
> > I could start doing that, it's going to be really noisy...
>
> It would need to exclude commits that are only in -next since that's a
> common legitimate use case for Fixes which shouldn't have a Cc to
> stable, and there's going to be a bunch of false positives from people
> who are overly enthusiastic in their use of fixes tags.
My scripts today already know where the original Fix tag came from, it's
not hard to detect. So this should not be an issue, we don't even
consider any commit with "Fixes:" in it for a kernel that has not
already been released.
thanks,
greg k-h
Powered by blists - more mailing lists