All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: Patch "watchdog: s3c2410_wdt: use exynos_get_pmu_regmap_by_phandle() for PMU regs" has been added to the 6.6-stable tree
Date: Sat, 4 Jan 2025 09:05:37 +0100	[thread overview]
Message-ID: <2025010457-runaround-wriggly-d117@gregkh> (raw)
In-Reply-To: <CADrjBPo_oiqboE4jAemR_2AjxJtSgMLpS8_ShWcX8wJLB4rszg@mail.gmail.com>

On Fri, Jan 03, 2025 at 04:46:54PM +0000, Peter Griffin wrote:
> Hi Sasha,
> 
> + cc stable@vger.kernel.org
> 
> On Fri, 3 Jan 2025 at 00:45, Sasha Levin <sashal@kernel.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> >     watchdog: s3c2410_wdt: use exynos_get_pmu_regmap_by_phandle() for PMU regs
> >
> > to the 6.6-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-use-exynos_get_pmu_regmap_by_ph.patch
> > and it can be found in the queue-6.6 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.
> 
> It doesn't make sense (to me at least) to add this patch and then also
> add the revert of it to v6.6 stable tree, as it becomes a no-op. The
> only reason I can think of is it somehow helps with your automated
> tooling?

This is exactly the reason.

> Additionally the hardware (Pixel 6 & gs101 SoC ) which these patches
> and APIs were added for wasn't merged until v6.8. The revert is also
> only applicable if the kernel has the corresponding enhancements made
> to syscon driver to register custom regmaps. See 769cb63166d9 ("mfd:
> syscon: Add of_syscon_register_regmap() API")

Ok, then we should just drop both, I can do that if you want me to.

thanks,

greg k-h

  reply	other threads:[~2025-01-04  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250103004519.474274-1-sashal@kernel.org>
2025-01-03 16:46 ` Patch "watchdog: s3c2410_wdt: use exynos_get_pmu_regmap_by_phandle() for PMU regs" has been added to the 6.6-stable tree Peter Griffin
2025-01-04  8:05   ` Greg KH [this message]
2025-01-06 13:35     ` Greg KH
2025-01-06 14:08       ` Peter Griffin

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=2025010457-runaround-wriggly-d117@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alim.akhtar@samsung.com \
    --cc=krzk@kernel.org \
    --cc=linux@roeck-us.net \
    --cc=peter.griffin@linaro.org \
    --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 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.