From: "Nuno Sá" <noname.nuno@gmail.com>
To: "David Lechner" <dlechner@baylibre.com>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>, "Mark Brown" <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 0/2] spi: axi-spi-engine: improve version checks
Date: Thu, 11 Sep 2025 17:23:07 +0100 [thread overview]
Message-ID: <a34a18e85fcaefe0e91bf5ac69806e113099d3d9.camel@gmail.com> (raw)
In-Reply-To: <20250815-spi-axi-spi-enigne-improve-version-checks-v1-0-13bde357d5b6@baylibre.com>
On Fri, 2025-08-15 at 12:40 -0500, David Lechner wrote:
> We have a pending major version bump for the axi-spi-engine so to
> prepare for that, improve the existing version checks for feature
> enablement.
>
> Unless Nuno knows something I don't, it should be fine for the header
> file patch to go through the SPI tree.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
> David Lechner (2):
> include: adi-axi-common: add version check function
> spi: axi-spi-engine: use adi_axi_pcore_ver_gteq()
>
> drivers/spi/spi-axi-spi-engine.c | 17 +++++++----------
> include/linux/adi-axi-common.h | 21 +++++++++++++++++++++
> 2 files changed, 28 insertions(+), 10 deletions(-)
> ---
> base-commit: bbe4656eae2729b8ca87116defa19c568898d08f
> change-id: 20250815-spi-axi-spi-enigne-improve-version-checks-cdceedf356d6
>
> Best regards,
LGTM,
Reviewed-by: Nuno Sá <nuno.sa@analog.com>
next prev parent reply other threads:[~2025-09-11 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 17:40 [PATCH 0/2] spi: axi-spi-engine: improve version checks David Lechner
2025-08-15 17:40 ` [PATCH 1/2] include: adi-axi-common: add version check function David Lechner
2025-08-15 17:40 ` [PATCH 2/2] spi: axi-spi-engine: use adi_axi_pcore_ver_gteq() David Lechner
2025-09-11 16:23 ` Nuno Sá [this message]
2025-09-12 3:30 ` [PATCH 0/2] spi: axi-spi-engine: improve version checks Mark Brown
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=a34a18e85fcaefe0e91bf5ac69806e113099d3d9.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=broonie@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.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