public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: "Nuno Sá via B4 Relay" <devnull+nuno.sa.analog.com@kernel.org>,
	dmaengine@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-fpga@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-pwm@vger.kernel.org,
	linux-spi@vger.kernel.org, nuno.sa@analog.com
Cc: "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>,
	"David Lechner" <dlechner@baylibre.com>,
	"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 RESEND v7 0/7] clk: clk-axi-clkgen: improvements and some fixes
Date: Sun, 21 Sep 2025 10:28:23 -0700	[thread overview]
Message-ID: <175847570323.4354.7019519707280531872@lazor> (raw)
In-Reply-To: <20250627-dev-axi-clkgen-limits-v7-0-e4f3b1f76189@analog.com>

Quoting Nuno Sá via B4 Relay (2025-06-27 07:59:09)
> 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().
> ---
> Changes in v7:
>  - Just include new tags.
> 
> - Link to v6: https://lore.kernel.org/r/20250519-dev-axi-clkgen-limits-v6-0-bc4b3b61d1d4@analog.com
> - Link to v5: https://lore.kernel.org/r/20250512-dev-axi-clkgen-limits-v5-0-a86b9a368e05@analog.com
> - Link to v4: https://lore.kernel.org/r/20250505-dev-axi-clkgen-limits-v4-0-3ad5124e19e1@analog.com
> - Link to v3: https://lore.kernel.org/r/20250421-dev-axi-clkgen-limits-v3-0-4203b4fed2c9@analog.com
> - Link to v2: https://lore.kernel.org/r/20250313-dev-axi-clkgen-limits-v2-0-173ae2ad6311@analog.com
> - Link to v1: https://lore.kernel.org/r/20250219-dev-axi-clkgen-limits-v1-0-26f7ef14cd9c@analog.com
> 
> ---
> Nuno Sá (7):
>       clk: clk-axi-clkgen: fix fpfd_max frequency for zynq
>       clk: clk-axi-clkgen: make sure to include mod_devicetable.h
>       include: linux: move adi-axi-common.h out of fpga
>       include: adi-axi-common: add new helper macros
>       clk: clk-axi-clkgen: detect axi_clkgen_limits at runtime
>       clk: clk-axi-clkgen move to min/max()
>       clk: clk-axi-clkgen: fix coding style issues

What is the merge strategy for this series?

> 
> 
>  drivers/clk/clk-axi-clkgen.c        | 159 +++++++++++++++++++++++++-----------
>  drivers/dma/dma-axi-dmac.c          |   2 +-
>  drivers/hwmon/axi-fan-control.c     |   2 +-
>  drivers/iio/adc/adi-axi-adc.c       |   3 +-
>  drivers/iio/dac/adi-axi-dac.c       |   2 +-
>  drivers/pwm/pwm-axi-pwmgen.c        |   2 +-
>  drivers/spi/spi-axi-spi-engine.c    |   2 +-
>  include/linux/adi-axi-common.h      |  56 +++++++++++++
>  include/linux/fpga/adi-axi-common.h |  23 ------
>  9 files changed, 174 insertions(+), 77 deletions(-)
> ---
> base-commit: 82f69876ef45ad66c0b114b786c7c6ac0f6a4580
> change-id: 20250218-dev-axi-clkgen-limits-63fb0c5ec38b

  parent reply	other threads:[~2025-09-21 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 14:59 [PATCH RESEND v7 0/7] clk: clk-axi-clkgen: improvements and some fixes Nuno Sá via B4 Relay
2025-06-27 14:59 ` [PATCH RESEND v7 1/7] clk: clk-axi-clkgen: fix fpfd_max frequency for zynq Nuno Sá via B4 Relay
2025-06-27 14:59 ` [PATCH RESEND v7 2/7] clk: clk-axi-clkgen: make sure to include mod_devicetable.h Nuno Sá via B4 Relay
2025-06-27 14:59 ` [PATCH RESEND v7 3/7] include: linux: move adi-axi-common.h out of fpga Nuno Sá via B4 Relay
2025-09-21 20:21   ` Uwe Kleine-König
2025-06-27 14:59 ` [PATCH RESEND v7 4/7] include: adi-axi-common: add new helper macros Nuno Sá via B4 Relay
2025-06-27 14:59 ` [PATCH RESEND v7 5/7] clk: clk-axi-clkgen: detect axi_clkgen_limits at runtime Nuno Sá via B4 Relay
2025-06-27 14:59 ` [PATCH RESEND v7 6/7] clk: clk-axi-clkgen move to min/max() Nuno Sá via B4 Relay
2025-06-27 14:59 ` [PATCH RESEND v7 7/7] clk: clk-axi-clkgen: fix coding style issues Nuno Sá via B4 Relay
2025-09-21 17:28 ` Stephen Boyd [this message]
2025-09-22 22:21   ` [PATCH RESEND v7 0/7] clk: clk-axi-clkgen: improvements and some fixes David Lechner

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=175847570323.4354.7019519707280531872@lazor \
    --to=sboyd@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=broonie@kernel.org \
    --cc=devnull+nuno.sa.analog.com@kernel.org \
    --cc=dlechner@baylibre.com \
    --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=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