From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: "Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] hwtracing: Switch back to struct platform_driver::remove()
Date: Thu, 9 Jan 2025 10:58:02 +0000 [thread overview]
Message-ID: <b1beee50-2f7d-4f5a-9bb0-20f0659a1240@arm.com> (raw)
In-Reply-To: <a4168463-98e3-4048-bb38-ffc96983766f@arm.com>
On 11/11/2024 14:47, Suzuki K Poulose wrote:
> Hi
>
> On 11/11/2024 14:12, Alexander Shishkin wrote:
>> Uwe Kleine-König <u.kleine-koenig@baylibre.com> writes:
>>
>>> After commit 0edb555a65d1 ("platform: Make platform_driver::remove()
>>> return void") .remove() is (again) the right callback to implement for
>>> platform drivers.
>>>
>>> Convert all platform drivers below drivers/hwtracing to use .remove(),
>>> with the eventual goal to drop struct platform_driver::remove_new(). As
>>> .remove() and .remove_new() have the same prototypes, conversion is done
>>> by just changing the structure member name in the driver initializer.
>>>
>>> Also adapt some whitespace to make indention consistent.
>>>
>>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
>>
>> Acked-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
>>
>>> ---
>>> Hello,
>>>
>>> I did a single patch for all of drivers/hwtracing. While I usually
>>> prefer to do one logical change per patch, this seems to be
>>> overengineering here as the individual changes are really trivial and
>>> shouldn't be much in the way for stable backports. But I'll happily
>>> split the patch if you prefer it split. Maybe split for coresight vs.
>>> intel_th? Also if you object the indentation stuff, I can rework that.
>>
>> I'm fine with it as is.
>>
>>> This is based on today's next, if conflicts arise when you apply it at
>>> some later time and don't want to resolve them, feel free to just drop
>>> the changes to the conflicting files. I'll notice and followup at a
>>> later time then. Or ask me for a fixed resend. (Having said that, I
>>> recommend b4 am -3 + git am -3 which should resolve most conflicts just
>>> fine.)
>>
>> Does anybody want to pick this up or should I? I'm fine either way, but
>> if there are any conflicts they won't be from my end of things, so it
>> might make sense to take it via the coresight path.
>
> I am happy to take them via coresight tree and queue them for v6.14
I see that Linus has queued this already
Suzuki
>
> Suzuki
>
>>
>> Thanks,
>> --
>> Alex
>
prev parent reply other threads:[~2025-01-09 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 11:09 Uwe Kleine-König
2024-11-11 14:12 ` Alexander Shishkin
2024-11-11 14:47 ` Suzuki K Poulose
2025-01-09 10:58 ` Suzuki K Poulose [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=b1beee50-2f7d-4f5a-9bb0-20f0659a1240@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.org \
--cc=u.kleine-koenig@baylibre.com \
/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®