public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Kristina Martsenko <kristina.martsenko@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	james.morse@arm.com, mark.rutland@arm.com, amit.kachhap@arm.com,
	maz@kernel.org, anshuman.khandual@arm.com, joey.gouly@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH AUTOSEL 6.4 07/12] arm64: cpufeature: detect FEAT_HCX
Date: Mon, 10 Jul 2023 16:09:06 +0200	[thread overview]
Message-ID: <2023071004-engaged-garter-171c@gregkh> (raw)
In-Reply-To: <0404e7ef-8b1f-483c-a167-56140b29f0cc@sirena.org.uk>

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

  reply	other threads:[~2023-07-10 14:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 19:50 [PATCH AUTOSEL 6.4 01/12] platform/chrome: cros_ec: Report EC panic as uevent Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 02/12] ACPI: x86: Add skip i2c clients quirk for Nextbook Ares 8A Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 03/12] ACPI: button: Add lid disable DMI " Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 04/12] ACPI: x86: Add ACPI_QUIRK_UART1_SKIP for Lenovo Yoga Book yb1-x90f/l Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 05/12] ACPI: video: Add backlight=native DMI quirk for Apple iMac11,3 Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 06/12] ACPI: video: Add backlight=native DMI quirk for Lenovo ThinkPad X131e (3371 AMD version) Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 07/12] arm64: cpufeature: detect FEAT_HCX Sasha Levin
2023-07-03 11:51   ` Mark Brown
2023-07-09 14:56     ` Sasha Levin
2023-07-09 21:13       ` Mark Brown
2023-07-10  9:44         ` Will Deacon
2023-07-10 13:31           ` Greg KH
2023-07-10 13:47             ` Mark Brown
2023-07-10 14:09               ` Greg KH [this message]
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 08/12] ACPI: resource: Remove "Zen" specific match and quirks Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 09/12] arm64: set __exception_irq_entry with __irq_entry as a default Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 10/12] arm64: mm: fix VA-range sanity check Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 11/12] drivers/perf: hisi: Add support for HiSilicon H60PA and PAv3 PMU driver Sasha Levin
2023-07-03 10:14   ` Mark Rutland
2023-07-21 15:13     ` Sasha Levin
2023-07-02 19:50 ` [PATCH AUTOSEL 6.4 12/12] ACPI: video: Add backlight=native DMI quirk for Dell Studio 1569 Sasha Levin
2023-07-10 22:46 ` [PATCH AUTOSEL 6.4 01/12] platform/chrome: cros_ec: Report EC panic as uevent Brian Norris
2023-07-21 15:11   ` Sasha Levin

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=2023071004-engaged-garter-171c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.kachhap@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kristina.martsenko@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will@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