From: "Kumar, Udit" <u-kumar1@ti.com>
To: Hemanth Selam <hemanth.selam@gmail.com>, <nm@ti.com>,
<ssantosh@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>
Subject: Re: [PATCH v2] soc: ti: knav_qmss_queue: Fix typos in comments
Date: Thu, 10 Sep 2026 19:54:50 +0530 [thread overview]
Message-ID: <96b806d6-242d-402e-be28-53f42be29883@ti.com> (raw)
In-Reply-To: <20260910044551.50308-1-hemanth.selam@gmail.com>
On 9/10/2026 10:15 AM, Hemanth Selam wrote:
> Correct "specifes" to "specifies" in the knav_queue_open() kernel-doc and
> "accomodate" to "accommodate" in knav_pool_create(). No code changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
> v2:
> - use the subject convention this file already follows, which names the
> driver and capitalises the description (Nishanth Menon)
I suggest using
soc: ti: knav_qmss: in subject instead of knav_qmss_queue
as most recent commits are following this convention
> - also correct "specifes" in the knav_queue_open() kernel-doc, so the
> file is done in one go rather than a patch per word (Nishanth Menon)
>
> codespell reports nothing else in this file. The remaining hits under
> drivers/soc/ti/ are in other drivers and are left for a separate patch;
> "indx" in k3-ringacc.c is a struct field name, not a typo.
>
> v1: https://lore.kernel.org/all/20260907062247.9994-1-hemanth.selam@gmail.com/
>
> drivers/soc/ti/knav_qmss_queue.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/ti/knav_qmss_queue.c b/drivers/soc/ti/knav_qmss_queue.c
> index 3e4041454f69..6186454dff51 100644
> --- a/drivers/soc/ti/knav_qmss_queue.c
> +++ b/drivers/soc/ti/knav_qmss_queue.c
> @@ -509,7 +509,7 @@ static int knav_queue_flush(struct knav_queue *qh)
> /**
> * knav_queue_open() - open a hardware queue
> * @name: - name to give the queue handle
> - * @id: - desired queue number if any or specifes the type
> + * @id: - desired queue number if any or specifies the type
> * of queue
> * @flags: - the following flags are applicable to queues:
> * KNAV_QUEUE_SHARED - allow the queue to be shared. Queues are
> @@ -805,7 +805,7 @@ void *knav_pool_create(const char *name,
> }
>
> /* Region maintains a sorted (by region offset) list of pools
> - * use the first free slot which is large enough to accomodate
> + * use the first free slot which is large enough to accommodate
> * the request
> */
> last_offset = 0;
prev parent reply other threads:[~2026-09-10 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 4:45 [PATCH v2] soc: ti: knav_qmss_queue: Fix typos in comments Hemanth Selam
2026-09-10 14:24 ` Kumar, Udit [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=96b806d6-242d-402e-be28-53f42be29883@ti.com \
--to=u-kumar1@ti.com \
--cc=hemanth.selam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).