From: Tarun Sahu <tarunsahu@google.com>
To: helgaas@kernel.org, dmatlack@google.com,
Nicholas Piggin <npiggin@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
sourabhjain@linux.ibm.com,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Russell King <linux@armlinux.org.uk>,
radheys@amd.com, skhawaja@google.com, djeffery@redhat.com,
Geoff Levand <geoff@infradead.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-arm-kernel@lists.infradead.org, souravsgl@google.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
driver-core@lists.linux.dev, Tarun Sahu <tarunsahu@google.com>
Subject: [PATCH v3 0/3] Convert manual kfree(dev) to put_device()
Date: Fri, 14 Aug 2026 21:00:54 +0000 [thread overview]
Message-ID: <20260814210057.4102768-1-tarunsahu@google.com> (raw)
Hello,
As per the kernel-doc guidelines, Devices that are tried to register
with device_register or to add using device_add, must use put_device
on their failure path (not kfree). This series contains 3 patches
for updating such instances. Same for kobject_init_and_add or
kobject_add, call kobject_put instead of kfree in case of error.
V3<-V1
1. Updated the commit msg of each patch to mention about the kernel-doc
guidelines.
V2 <- V1
1. Removed patch [1] as it is part of another series [2] already.
[1]: https://lore.kernel.org/all/20260810162814.1398016-4-tarunsahu@google.com/
[2]: https://lore.kernel.org/all/20260724171945.2812749-5-shubhrajyoti.datta@amd.com/
Tarun Sahu (3):
ARM: locomo: use put_device() on device_register() failure
firmware/edd: use kobject_put() on edd_device_register() failure
powerpc/ps3: use put_device() on device_register() failure in
ps3_system_bus_device_register
arch/arm/common/locomo.c | 13 ++--
arch/powerpc/platforms/ps3/device-init.c | 83 ++++++++++++++----------
arch/powerpc/platforms/ps3/system-bus.c | 2 +
drivers/firmware/edd.c | 2 +-
4 files changed, 59 insertions(+), 41 deletions(-)
base-commit: ddca0cd800962b4121e5f2633005167bb6216175
--
2.55.0.691.gc56d675ccc-goog
next reply other threads:[~2026-08-14 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 21:00 Tarun Sahu [this message]
2026-08-14 21:00 ` [PATCH v3 1/3] ARM: locomo: use put_device() on device_register() failure Tarun Sahu
2026-08-14 21:00 ` [PATCH v3 2/3] firmware/edd: use kobject_put() on edd_device_register() failure Tarun Sahu
2026-08-14 22:06 ` Bjorn Helgaas
2026-08-14 21:00 ` [PATCH v3 3/3] powerpc/ps3: use put_device() on device_register() failure in ps3_system_bus_device_register Tarun Sahu
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=20260814210057.4102768-1-tarunsahu@google.com \
--to=tarunsahu@google.com \
--cc=chleroy@kernel.org \
--cc=djeffery@redhat.com \
--cc=dmatlack@google.com \
--cc=driver-core@lists.linux.dev \
--cc=geoff@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=pasha.tatashin@soleen.com \
--cc=radheys@amd.com \
--cc=skhawaja@google.com \
--cc=sourabhjain@linux.ibm.com \
--cc=souravsgl@google.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