From: Markus Elfring <Markus.Elfring@web.de>
To: Johan Hovold <johan@kernel.org>, asahi@lists.linux.dev
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Janne Grunau <j@jannau.net>, Neal Gompa <neal@gompa.dev>,
Sven Peter <sven@kernel.org>
Subject: Re: [PATCH 1/2] soc: apple: mailbox: fix device leak on lookup
Date: Fri, 26 Sep 2025 20:08:06 +0200 [thread overview]
Message-ID: <13b7276a-f151-4b03-9f90-847d4a4aa031@web.de> (raw)
In-Reply-To: <20250926143132.6419-2-johan@kernel.org>
> Make sure to drop the reference taken to the mbox platform device when
> looking up its driver data.
…
How do you think about to increase the application of scope-based resource management?
https://elixir.bootlin.com/linux/v6.17-rc7/source/include/linux/device.h#L1180
https://elixir.bootlin.com/linux/v6.17-rc7/source/include/linux/of.h#L138
Regards,
Markus
prev parent reply other threads:[~2025-09-26 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250926143132.6419-1-johan@kernel.org>
2025-09-26 14:31 ` [PATCH 1/2] soc: apple: mailbox: fix device leak on lookup Johan Hovold
2025-09-26 18:08 ` Markus Elfring [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=13b7276a-f151-4b03-9f90-847d4a4aa031@web.de \
--to=markus.elfring@web.de \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neal@gompa.dev \
--cc=stable@vger.kernel.org \
--cc=sven@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