From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
alexander.shishkin@linux.intel.com
Subject: Re: [PATCH 7/8] intel_th: Convert to platform remove callback returning void
Date: Mon, 29 Apr 2024 15:22:08 +0300 [thread overview]
Message-ID: <871q6owe8f.fsf@ubik.fi.intel.com> (raw)
In-Reply-To: <rucgdqb5ejtttsd2ksvph3toeow652rdiqnohdsg6ndp6qgcwu@c3rz275bofqg>
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
> Hello Alex,
Hi Uwe,
> On Mon, Apr 15, 2024 at 09:48:27AM +0300, Alexander Shishkin wrote:
>> Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
>> > Given there are not that many patches left (~50) as of today's next, I'd
>> > like to see this patch going in during the next merge window, that I can
>> > finalize the (next step of the) quest around platform_driver::remove.
>> >
>> > Is sending this patch to Greg still on your todo list?
>>
>> Yes, as soon as I finalize other patches on my series. Should be soon.
>
> I know neither your nor Greg's plans, but I wonder if this patch will
> make it into v6.10-rc1 given that it still didn't land in next yet.
I've just sent my series [0].
> I intend to change the prototype of platform_driver::remove() after the
> merge window leading to v6.10-rc1 closes to cook in next for some time.
> If this patch doesn't make it into the mainline before, I'll send it
> together with the change adapting the remove callback. That will go in
> via Greg's tree, too.
I saw that you included this patch with your series earlier today, so I
dropped it from my series [0]. FWIW, you can add
Acked-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
to that patch if it helps. If you want me to pick it up again, let me
know. Apologies for the repeated tardiness in handling this.
[0] https://lore.kernel.org/all/20240429120908.3723458-1-alexander.shishkin@linux.intel.com/
Regards,
--
Alex
next prev parent reply other threads:[~2024-04-29 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231107202818.4005791-1-u.kleine-koenig@pengutronix.de>
2023-11-07 20:28 ` [PATCH 7/8] intel_th: Convert to platform remove callback returning void Uwe Kleine-König
2024-01-10 8:41 ` Uwe Kleine-König
2024-02-15 21:16 ` Uwe Kleine-König
2024-02-21 7:19 ` Uwe Kleine-König
2024-02-21 18:50 ` Alexander Shishkin
2024-04-11 7:07 ` Uwe Kleine-König
2024-04-15 6:48 ` Alexander Shishkin
2024-04-29 7:13 ` Uwe Kleine-König
2024-04-29 12:22 ` Alexander Shishkin [this message]
2024-04-29 12:30 ` Alexander Shishkin
2024-04-29 13:07 ` Alexander Shishkin
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=871q6owe8f.fsf@ubik.fi.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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