All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: Sean Anderson <seanga2@gmail.com>, u-boot@lists.denx.de
Cc: "Ramon Fried" <rfried.dev@gmail.com>,
	"Joe Hershberger" <joe.hershberger@ni.com>,
	"Daniel Schwierzeck" <daniel.schwierzeck@gmail.com>,
	"Jagan Teki" <jagan@amarulasolutions.com>,
	"Lukasz Majewski" <lukma@denx.de>,
	"Álvaro Fernández Rojas" <noltari@gmail.com>,
	"Simon Glass" <sjg@chromium.org>
Subject: Re: [PATCH 0/7] clk: Make clk_free return void
Date: Wed, 30 Mar 2022 15:21:51 -0400	[thread overview]
Message-ID: <164866411209.441601.3349958857188274518.b4-ty@gmail.com> (raw)
In-Reply-To: <20220115222504.617013-1-seanga2@gmail.com>

On Sat, 15 Jan 2022 17:24:57 -0500, Sean Anderson wrote:
> 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
> 
> [...]

Applied, thanks!

[1/7] clk: Make rfree return void
      commit: 276d446757e462c210768eb0bbd48450ae254f51
[2/7] dma: bcm6348: Don't check clk_free
      commit: 454af567edc0b02842c83aaf1a60bbcb766af0cd
[3/7] net: bcm63xx: Don't check clk_free
      commit: b2e0889abacfd453131359156fe279996727d95b
[4/7] phy: bcm63xx: Don't check clk_free
      commit: ad20358c7462159d5f9012facba9dec1e197aaca
[5/7] spi: bcm63xx: Don't check clk_free
      commit: dfdb227c3d018983f37cc97fe003e231a81a46ea
[6/7] spi: dw: Don't check clk_free
      commit: 3cbdd4cab951b8bd3f2e76066e6911f9780c4eb1
[7/7] clk: Make clk_free return void
      commit: ac15e789caecec19d29ee9c5869305d3c3ddfb42

Best regards,
-- 
Sean Anderson <seanga2@gmail.com>

      parent reply	other threads:[~2022-03-30 19:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 22:24 [PATCH 0/7] clk: Make clk_free return void Sean Anderson
2022-01-15 22:24 ` [PATCH 1/7] clk: Make rfree " 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 ` Sean Anderson [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=164866411209.441601.3349958857188274518.b4-ty@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 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.