From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Cc: "Simon Glass" <sjg@chromium.org>,
"Lukasz Majewski" <lukma@denx.de>,
"Sean Anderson" <seanga2@gmail.com>,
"Daniel Schwierzeck" <daniel.schwierzeck@gmail.com>,
"Jagan Teki" <jagan@amarulasolutions.com>,
"Joe Hershberger" <joe.hershberger@ni.com>,
"Ramon Fried" <rfried.dev@gmail.com>,
"Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH 0/7] clk: Make clk_free return void
Date: Sat, 15 Jan 2022 17:24:57 -0500 [thread overview]
Message-ID: <20220115222504.617013-1-seanga2@gmail.com> (raw)
clk_free cleans up resources allocated by clk_request et. al. It returns an
error code, but it really shouldn't. Much like regular free(), there is
typically no way to handle an error, and errors from clk_free shouldn't prevent
progress in the rest of the program. Make clk_free (and rfree) return void.
Sean Anderson (7):
clk: Make rfree return void
dma: bcm6348: Don't check clk_free
net: bcm63xx: Don't check clk_free
phy: bcm63xx: Don't check clk_free
spi: bcm63xx: Don't check clk_free
spi: dw: Don't check clk_free
clk: Make clk_free return void
drivers/clk/clk-uclass.c | 15 ++++++---------
drivers/clk/clk_sandbox.c | 6 +++---
drivers/clk/clk_sandbox_test.c | 9 +++------
drivers/dma/bcm6348-iudma.c | 6 +-----
drivers/net/bcm6348-eth.c | 6 +-----
drivers/net/bcm6368-eth.c | 6 +-----
drivers/phy/bcm6318-usbh-phy.c | 4 +---
drivers/phy/bcm6348-usbh-phy.c | 4 +---
drivers/phy/bcm6368-usbh-phy.c | 8 ++------
drivers/spi/bcm63xx_hsspi.c | 8 ++------
drivers/spi/bcm63xx_spi.c | 4 +---
drivers/spi/designware_spi.c | 2 +-
include/clk-uclass.h | 8 +++-----
include/clk.h | 8 ++++----
14 files changed, 30 insertions(+), 64 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-15 22:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 22:24 Sean Anderson [this message]
2022-01-15 22:24 ` [PATCH 1/7] clk: Make rfree return void Sean Anderson
2022-01-27 15:05 ` Simon Glass
2022-01-27 15:42 ` Sean Anderson
2022-01-27 21:35 ` Simon Glass
2022-02-01 14:49 ` Sean Anderson
2022-02-02 3:59 ` Simon Glass
2022-02-02 4:24 ` Sean Anderson
2022-02-26 18:36 ` Simon Glass
2022-02-27 19:38 ` Sean Anderson
2022-03-01 14:58 ` Simon Glass
2022-03-16 16:18 ` Sean Anderson
2022-03-16 19:23 ` Simon Glass
2022-01-15 22:24 ` [PATCH 2/7] dma: bcm6348: Don't check clk_free Sean Anderson
2022-01-15 22:25 ` [PATCH 3/7] net: bcm63xx: " Sean Anderson
2022-01-15 22:25 ` [PATCH 4/7] phy: " Sean Anderson
2022-01-15 22:25 ` [PATCH 5/7] spi: " Sean Anderson
2022-01-15 22:25 ` [PATCH 6/7] spi: dw: " Sean Anderson
2022-01-15 22:25 ` [PATCH 7/7] clk: Make clk_free return void Sean Anderson
2022-03-30 19:21 ` [PATCH 0/7] " Sean Anderson
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=20220115222504.617013-1-seanga2@gmail.com \
--to=seanga2@gmail.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=joe.hershberger@ni.com \
--cc=lukma@denx.de \
--cc=noltari@gmail.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox