All of lore.kernel.org
 help / color / mirror / Atom feed
From: Triet Hoang <triet.hoang.dev@gmail.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Stefan Wahren <wahrenst@gmx.net>,
	Triet Hoang <triet.hoang.dev@gmail.com>
Subject: [PATCH 0/2] firmware: raspberrypi: Handle device registration errors
Date: Sat, 19 Sep 2026 03:48:38 +0000	[thread overview]
Message-ID: <20260919034840.28593-1-triet.hoang.dev@gmail.com> (raw)

Hi,

This series improves error handling when registering the Raspberry Pi
firmware hwmon and clock platform devices.

The first patch checks errors returned by platform_device_register_data()
and unwinds previously allocated resources when registration fails. It
preserves the existing behavior of skipping hwmon registration when the
RPI_FIRMWARE_GET_THROTTLED request fails.

The second patch fixes formatting issues reported by checkpatch.

Triet Hoang (2):
  firmware: raspberrypi: Handle device registration errors
  firmware: raspberrypi: Clean up local formatting

 drivers/firmware/raspberrypi.c | 60 ++++++++++++++++++++++++++--------
 1 file changed, 46 insertions(+), 14 deletions(-)

-- 
2.53.0



             reply	other threads:[~2026-09-19  3:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  3:48 Triet Hoang [this message]
2026-09-19  3:48 ` [PATCH 1/2] firmware: raspberrypi: Handle device registration errors Triet Hoang
2026-09-19 16:05   ` Stefan Wahren
2026-09-19  3:48 ` [PATCH 2/2] firmware: raspberrypi: Clean up local formatting Triet Hoang
2026-09-19 16:06   ` Stefan Wahren
2026-09-22 14:22   ` Markus Elfring
2026-10-02 15:13     ` Stefan Wahren
2026-10-03 11:17       ` [2/2] " Markus Elfring
2026-10-03 13:34         ` Stefan Wahren

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=20260919034840.28593-1-triet.hoang.dev@gmail.com \
    --to=triet.hoang.dev@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=wahrenst@gmx.net \
    /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.