From: Stephen Boyd <sboyd@kernel.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>,
kristo@kernel.org, luca.ceresoli@bootlin.com,
michal.simek@xilinx.com, mturquette@baylibre.com, nm@ti.com,
ssantosh@kernel.org
Cc: aford173@gmail.com, mike.looijmans@topic.nl,
robert.hancock@calian.com, shawn.guo@linaro.org,
fabio.estevam@freescale.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: Re: [PATCH 3/8] clk: si5341: return error if one synth clock registration fails
Date: Tue, 20 Jun 2023 11:54:28 -0700 [thread overview]
Message-ID: <ff48113a0f4fffbd73fe96a3889734da.sboyd@kernel.org> (raw)
In-Reply-To: <20230530093913.1656095-4-claudiu.beznea@microchip.com>
Quoting Claudiu Beznea (2023-05-30 02:39:08)
> In case devm_clk_hw_register() fails for one of synth clocks the probe
> continues. Later on, when registering output clocks which have as parents
> all the synth clocks, in case there is registration failure for at least
> one synth clock the information passed to clk core for registering output
> clock is not right: init.num_parents is fixed but init.parents may contain
> an array with less parents.
>
> Fixes: 3044a860fd09 ("clk: Add Si5341/Si5340 driver")
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
Applied to clk-next
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-20 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 9:39 [PATCH 0/8] clk: check memory returned by {devm_}kasprintf() Claudiu Beznea
2023-05-30 9:39 ` [PATCH 1/8] clk: vc5: check memory returned by kasprintf() Claudiu Beznea
2023-05-31 16:32 ` Luca Ceresoli
2023-06-20 18:53 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 2/8] clk: cdce925: check return value of kasprintf() Claudiu Beznea
2023-06-20 18:54 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 3/8] clk: si5341: return error if one synth clock registration fails Claudiu Beznea
2023-06-20 18:54 ` Stephen Boyd [this message]
2023-05-30 9:39 ` [PATCH 4/8] clk: si5341: check return value of {devm_}kasprintf() Claudiu Beznea
2023-06-20 18:54 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 5/8] clk: si5341: free unused memory on probe failure Claudiu Beznea
2023-06-20 18:55 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 6/8] clk: keystone: sci-clk: check return value of kasprintf() Claudiu Beznea
2023-05-31 4:12 ` Tony Lindgren
2023-06-20 18:55 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 7/8] clk: ti: clkctrl: " Claudiu Beznea
2023-05-31 4:12 ` Tony Lindgren
2023-06-20 18:55 ` Stephen Boyd
2023-05-30 9:39 ` [PATCH 8/8] clk: clocking-wizard: check return value of devm_kasprintf() Claudiu Beznea
2023-06-20 18:55 ` Stephen Boyd
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=ff48113a0f4fffbd73fe96a3889734da.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=aford173@gmail.com \
--cc=claudiu.beznea@microchip.com \
--cc=fabio.estevam@freescale.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@xilinx.com \
--cc=mike.looijmans@topic.nl \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=robert.hancock@calian.com \
--cc=shawn.guo@linaro.org \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).