From: Greg KH <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
bt.cho@samsung.com, Alim Akhtar <alim.akhtar@samsung.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: Patch "watchdog: s3c2410_wdt: add support for exynosautov920 SoC" has been added to the 6.12-stable tree
Date: Mon, 30 Dec 2024 15:32:32 +0100 [thread overview]
Message-ID: <2024123026-ether-pushpin-a62e@gregkh> (raw)
In-Reply-To: <c7f22382-5a75-475f-a851-621fab2d0b27@kernel.org>
On Sun, Dec 29, 2024 at 10:42:07AM +0100, Krzysztof Kozlowski wrote:
> On 28/12/2024 15:20, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > watchdog: s3c2410_wdt: add support for exynosautov920 SoC
> >
> > to the 6.12-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > watchdog-s3c2410_wdt-add-support-for-exynosautov920-.patch
> > and it can be found in the queue-6.12 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> This is a new device support, depending on several other pieces like
> syscon support, Exynos PMU and of course arm64/boot/dts patches. It
> really relies on the rest of SoC support and alone is useless.
>
> This is way beyond simple quirks thus I believe it does not meet stable
> criteria at all.
>
> Based on that I recommend to drop this patch from stable backports.
Now dropped, thanks.
greg k-h
prev parent reply other threads:[~2024-12-30 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241228142016.3647634-1-sashal@kernel.org>
2024-12-29 9:42 ` Patch "watchdog: s3c2410_wdt: add support for exynosautov920 SoC" has been added to the 6.12-stable tree Krzysztof Kozlowski
2024-12-30 14:32 ` Greg KH [this message]
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=2024123026-ether-pushpin-a62e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alim.akhtar@samsung.com \
--cc=bt.cho@samsung.com \
--cc=krzk@kernel.org \
--cc=linux@roeck-us.net \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wim@linux-watchdog.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