mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: glink: use device_for_each_child_node_scoped()
Date: Thu, 27 Jun 2024 16:43:55 +0200	[thread overview]
Message-ID: <a9c93cd0-e0e9-44d4-a22c-948f5d01754b@gmail.com> (raw)
In-Reply-To: <2024062735-railway-stoning-566a@gregkh>

On 27/06/2024 16:11, Greg Kroah-Hartman wrote:
> On Sun, Jun 23, 2024 at 12:35:11PM +0200, Javier Carrasco wrote:
>> Use the scoped variant of `device_for_each_child_node()` to
>> automatically handle early exits.
>>
>> This prevents memory leaks if new error paths are introduced,
>> as no explicit refcount decrement via `fwnode_handle_put()` is needed.
>>
>> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
>> ---
>> This patch is a follow-up to the recently introduced commit c68942624e25
>> ("usb: typec: ucsi: glink: fix child node release in probe function")
>> to account for a safer approach to iterating over child nodes.
> 
> What branch/tree is this against?  It fails to apply to my usb-testing
> branch at all :(
> 
> Can you rebase and resubmit?
> 
> thanks,
> 
> greg k-h


Hi, for this to apply you need the commit c68942624e25 ("usb: typec:
ucsi: glink: fix child node release in probe function"), which still
uses a non-scoped macro to account for stable kernels. I mentioned it
under the --- separator, but maybe that is not the way to go.

This patch is a follow-up to use the scoped variant and avoid more bugs
when new early exits are added.

I thought the other patch had already been applied, but apparently not
to usb-testing (I used linux-next as basis, the base-commit can be found
below the patch).

Could you please apply the other patch first? If for whatever reason
that is not desired, I could resend both patches as a series to avoid
that one goes unnoticed, but as I said, the first one is already in
linux-next.

Best regards,
Javier Carrasco

      reply	other threads:[~2024-06-27 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 10:35 Javier Carrasco
2024-06-25 14:30 ` Heikki Krogerus
2024-06-27 14:11 ` Greg Kroah-Hartman
2024-06-27 14:43   ` Javier Carrasco [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=a9c93cd0-e0e9-44d4-a22c-948f5d01754b@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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®