All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
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,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 0/4] w1: Convert to platform remove callback returning void
Date: Tue, 20 Feb 2024 11:21:46 +0100	[thread overview]
Message-ID: <c0b6dd69-c52f-4da3-8eda-d6eeb544cb25@linaro.org> (raw)
In-Reply-To: <3eb8e209-3d86-41a3-b65c-58f0f24ad6b7@linaro.org>

On 20/02/2024 11:19, Krzysztof Kozlowski wrote:
> On 19/02/2024 21:25, Uwe Kleine-König wrote:
>> Hello,
>>
>> On Mon, Feb 19, 2024 at 11:59:26AM +0100, Uwe Kleine-König wrote:
>>> this series converts all drivers below drivers/w1 to struct
>>> platform_driver::remove_new(). See commit 5c5a7680e67b ("platform:
>>> Provide a remove callback that returns no value") for an extended
>>> explanation and the eventual goal.
>>>
>>> All four conversations are trivial, because their .remove() callbacks
>>> returned zero unconditionally. 
>>>
>>> There are no interdependencies between these patches, so they could be
>>> picked up individually. However I'd expect them to go in all together
>>> via Krzysztof's tree.
>>
>> This series hit a corner case in my patch sending scripts (because the
>> maintainer entry title has a ' which I failed to properly quote). I'll
>> try to resend the patches that didn't hit the mailing list.
> 
> I don't know what you are referring to. I don't think I ever received
> your patchset and from another patchset - linked here, but not marked as
> resend? - I got only two patches.
> 
> Please make a proper submission. Don't attach your patchsets to some
> other threads. If this is resend, add proper "RESEND PATCH" prefix.
> 

I think I got the rest of patches here, although this is still oddly
threaded.

Best regards,
Krzysztof


  reply	other threads:[~2024-02-20 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 10:59 [PATCH 0/4] w1: Convert to platform remove callback returning void Uwe Kleine-König
2024-02-19 10:59 ` [PATCH 2/4] w1: omap_hdq: " Uwe Kleine-König
2024-02-19 10:59 ` [PATCH 4/4] w1: w1-gpio: " Uwe Kleine-König
2024-02-19 20:25 ` [PATCH 0/4] w1: " Uwe Kleine-König
2024-02-20 10:19   ` Krzysztof Kozlowski
2024-02-20 10:21     ` Krzysztof Kozlowski [this message]
2024-02-19 20:28 ` [PATCH 1/4] w1: mxc_w1: " Uwe Kleine-König
2024-02-19 20:28 ` [PATCH 3/4] w1: sgi_w1: " Uwe Kleine-König
2024-02-20 10:25 ` [PATCH 0/4] w1: " Krzysztof Kozlowski

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=c0b6dd69-c52f-4da3-8eda-d6eeb544cb25@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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 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.