From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: David Lechner <dlechner@baylibre.com>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"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,
"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 v6 3/7] include: linux: move adi-axi-common.h out of fpga
Date: Tue, 16 Sep 2025 17:08:07 +0200 [thread overview]
Message-ID: <20250916150807090a7e5f@mail.local> (raw)
In-Reply-To: <711b5e34-3534-440c-8914-ddb41987ee8d@baylibre.com>
On 16/09/2025 09:55:13-0500, David Lechner wrote:
> On 9/16/25 8:04 AM, Alexandre Belloni wrote:
> > Hi Stephen,
> >
> > On 30/06/2025 17:58:56-0700, Stephen Boyd wrote:
> >> Quoting Nuno Sá via B4 Relay (2025-05-19 08:41:08)
> >>> From: Nuno Sá <nuno.sa@analog.com>
> >>>
> >>> The adi-axi-common.h header has some common defines used in various ADI
> >>> IPs. However they are not specific for any fpga manager so it's
> >>> questionable for the header to live under include/linux/fpga. Hence
> >>> let's just move one directory up and update all users.
> >>>
> >>> Suggested-by: Xu Yilun <yilun.xu@linux.intel.com>
> >>> Acked-by: Xu Yilun <yilun.xu@intel.com>
> >>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> # for IIO
> >>> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> >>> ---
> >>
> >> Applied to clk-next
> >
> > Do you mind providing an immutable branch for this as my i3c tree is
> > introducing a new driver using this header and so it is going to depend
> > on your branch.
> >
> > Thanks!
> >
>
> This was merged into mainline in v6.17-rc1, so I don't think we should
> need an immutable branch at this point.
>
> If you are modifying the include/linux/adi-axi-common.h file in the I3C
> tree, FYI there are some changes in the SPI tree that just got applied [1].
> But if you just need the header in the new location, it should already
> be there since v6.17-rc1.
>
Hum, right, this makes me realize I din't rebase i3c/next on top of
v6.17-rc1
>
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?id=67a529b7d3c50a56c162476509361f4fe11350dd
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-16 15:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 15:41 [PATCH v6 0/7] clk: clk-axi-clkgen: improvements and some fixes Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-05-19 15:41 ` [PATCH v6 1/7] clk: clk-axi-clkgen: fix fpfd_max frequency for zynq Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-07-01 0:58 ` Stephen Boyd
2025-05-19 15:41 ` [PATCH v6 2/7] clk: clk-axi-clkgen: make sure to include mod_devicetable.h Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-07-01 0:58 ` Stephen Boyd
2025-05-19 15:41 ` [PATCH v6 3/7] include: linux: move adi-axi-common.h out of fpga Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-05-19 15:57 ` Mark Brown
2025-05-19 16:28 ` Uwe Kleine-König
2025-07-01 0:58 ` Stephen Boyd
2025-09-16 13:04 ` Alexandre Belloni
2025-09-16 14:55 ` David Lechner
2025-09-16 15:08 ` Alexandre Belloni [this message]
2025-05-19 15:41 ` [PATCH v6 4/7] include: adi-axi-common: add new helper macros Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-07-01 0:59 ` Stephen Boyd
2025-05-19 15:41 ` [PATCH v6 5/7] clk: clk-axi-clkgen: detect axi_clkgen_limits at runtime Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-07-01 0:59 ` Stephen Boyd
2025-05-19 15:41 ` [PATCH v6 6/7] clk: clk-axi-clkgen move to min/max() Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-07-01 0:59 ` Stephen Boyd
2025-05-19 15:41 ` [PATCH v6 7/7] clk: clk-axi-clkgen: fix coding style issues Nuno Sá
2025-05-19 15:41 ` Nuno Sá via B4 Relay
2025-07-01 0:59 ` Stephen Boyd
2025-05-19 15:57 ` [PATCH v6 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=20250916150807090a7e5f@mail.local \
--to=alexandre.belloni@bootlin.com \
--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=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 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.