From: David Lechner <dlechner@baylibre.com>
To: nuno.sa@analog.com, linux-clk@vger.kernel.org,
linux-fpga@vger.kernel.org, dmaengine@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-iio@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-spi@vger.kernel.org
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Moritz Fischer" <mdf@kernel.org>, "Wu Hao" <hao.wu@intel.com>,
"Xu Yilun" <yilun.xu@intel.com>, "Tom Rix" <trix@redhat.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Jean Delvare" <jdelvare@suse.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Trevor Gamblin" <tgamblin@baylibre.com>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Mark Brown" <broonie@kernel.org>,
"Mike Turquette" <mturquette@linaro.org>,
"Xu Yilun" <yilun.xu@linux.intel.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v5 0/7] clk: clk-axi-clkgen: improvements and some fixes
Date: Mon, 12 May 2025 10:22:21 -0500 [thread overview]
Message-ID: <a810d8ff-535c-4d6c-bec3-8a275bcbe483@baylibre.com> (raw)
In-Reply-To: <20250512-dev-axi-clkgen-limits-v5-0-a86b9a368e05@analog.com>
On 5/12/25 9:46 AM, Nuno Sá via B4 Relay wrote:
> This series starts with a small fix and then a bunch of small
> improvements. The main change though is to allow detecting of
> struct axi_clkgen_limits during probe().
>
> ---
How we added the linux/adi-axi-common.h include to the clk-axi-clkgen
driver could have been tidier, but not strictly worth a v6 just for that.
Reviewed-by: David Lechner <dlechner@baylibre.com>
prev parent reply other threads:[~2025-05-12 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 14:46 [PATCH v5 0/7] clk: clk-axi-clkgen: improvements and some fixes Nuno Sá via B4 Relay
2025-05-12 14:46 ` [PATCH v5 1/7] clk: clk-axi-clkgen: fix fpfd_max frequency for zynq Nuno Sá via B4 Relay
2025-05-12 14:46 ` [PATCH v5 2/7] clk: clk-axi-clkgen: make sure to include mod_devicetable.h Nuno Sá via B4 Relay
2025-05-12 14:46 ` [PATCH v5 3/7] include: linux: move adi-axi-common.h out of fpga Nuno Sá via B4 Relay
2025-05-12 15:15 ` David Lechner
2025-05-13 6:59 ` Nuno Sá
2025-05-12 14:46 ` [PATCH v5 4/7] include: adi-axi-common: add new helper macros Nuno Sá via B4 Relay
2025-05-12 14:46 ` [PATCH v5 5/7] clk: clk-axi-clkgen: detect axi_clkgen_limits at runtime Nuno Sá via B4 Relay
2025-05-12 14:46 ` [PATCH v5 6/7] clk: clk-axi-clkgen move to min/max() Nuno Sá via B4 Relay
2025-05-12 14:46 ` [PATCH v5 7/7] clk: clk-axi-clkgen: fix coding style issues Nuno Sá via B4 Relay
2025-05-12 15:19 ` David Lechner
2025-05-12 15:22 ` David Lechner [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=a810d8ff-535c-4d6c-bec3-8a275bcbe483@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mdf@kernel.org \
--cc=mturquette@baylibre.com \
--cc=mturquette@linaro.org \
--cc=nuno.sa@analog.com \
--cc=sboyd@kernel.org \
--cc=tgamblin@baylibre.com \
--cc=trix@redhat.com \
--cc=ukleinek@kernel.org \
--cc=vkoul@kernel.org \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.intel.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