From: Josh Law <hlcj1234567@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Josh Law <objecting@objecting.org>
Subject: [PATCH 1/4] staging: axis-fifo: fix grammar in Kconfig help text
Date: Sun, 1 Mar 2026 15:53:15 +0000 [thread overview]
Message-ID: <20260301155318.2596519-1-objecting@objecting.org> (raw)
Use 'an' instead of 'a' before 'AXI' since it begins with a vowel sound.
Signed-off-by: Josh Law <objecting@objecting.org>
---
drivers/staging/axis-fifo/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/axis-fifo/Kconfig b/drivers/staging/axis-fifo/Kconfig
index f180a8e9f58a..e618f275e283 100644
--- a/drivers/staging/axis-fifo/Kconfig
+++ b/drivers/staging/axis-fifo/Kconfig
@@ -7,6 +7,6 @@ config XIL_AXIS_FIFO
depends on OF && HAS_IOMEM
help
This adds support for the Xilinx AXI-Stream FIFO IP core driver.
- The AXI Streaming FIFO allows memory mapped access to a AXI Streaming
+ The AXI Streaming FIFO allows memory mapped access to an AXI Streaming
interface. The Xilinx AXI-Stream FIFO IP core can be used to interface
to the AXI Ethernet without the need to use DMA.
--
2.43.0
next reply other threads:[~2026-03-01 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 15:53 Josh Law [this message]
2026-03-01 15:53 ` [PATCH 2/4] staging: axis-fifo: use lowercase hex constant for consistency Josh Law
2026-03-01 15:53 ` [PATCH 3/4] staging: axis-fifo: remove unnecessary variable initializations Josh Law
2026-03-01 15:53 ` [PATCH 4/4] staging: axis-fifo: simplify error returns in axis_fifo_parse_dt() Josh Law
2026-03-01 18:46 ` [PATCH 1/4] staging: axis-fifo: fix grammar in Kconfig help text Ethan Tidmore
2026-03-01 18:54 ` Josh Law
2026-03-01 21:27 ` Ethan Tidmore
2026-03-01 23:49 ` Bagas Sanjaya
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=20260301155318.2596519-1-objecting@objecting.org \
--to=hlcj1234567@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=objecting@objecting.org \
--cc=ovidiu.panait.oss@gmail.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