From: Philipp Zabel <p.zabel@pengutronix.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
David Lechner <david@lechnology.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 0/2] reset: remove last remaining user of the legacy lookup and drop unused code
Date: Thu, 30 Oct 2025 13:55:32 +0100 [thread overview]
Message-ID: <02c89eed4c8f8ee5b4fb1d2e7d6956eb6a562d23.camel@pengutronix.de> (raw)
In-Reply-To: <20251022-da850-reset-lookup-v2-0-c80f03831f63@linaro.org>
On Mi, 2025-10-22 at 15:51 +0200, Bartosz Golaszewski wrote:
> The TI DaVinci platform is the only remaining user of reset platform
> lookup. Except that we no longer have any legacy, non-DT boards in
> mainline so we can now safely remove it from the PSC driver and drop the
> legacy lookup support from reset core.
>
> The DaVinci clock driver doesn't see a lot of traffic these days so I
> suggest a simple Ack from the clock maintainers and routing it through
> the reset core for v6.19.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Applied to reset/next, thanks!
[1/2] clk: davinci: psc: drop unused reset lookup
https://git.pengutronix.de/cgit/pza/linux/commit/?id=d8b79ad1f40c
[2/2] reset: remove legacy reset lookup code
https://git.pengutronix.de/cgit/pza/linux/commit/?id=205b261463ff
regards
Philipp
prev parent reply other threads:[~2025-10-30 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 13:51 Bartosz Golaszewski
2025-10-22 13:51 ` [PATCH v2 1/2] clk: davinci: psc: drop unused reset lookup Bartosz Golaszewski
2025-10-23 15:09 ` David Lechner
2025-10-24 7:53 ` Bartosz Golaszewski
2025-10-26 1:38 ` Stephen Boyd
2025-10-22 13:51 ` [PATCH v2 2/2] reset: remove legacy reset lookup code Bartosz Golaszewski
2025-10-30 12:55 ` Philipp Zabel [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=02c89eed4c8f8ee5b4fb1d2e7d6956eb6a562d23.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®