From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
matt@codeconstruct.com.au, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: mctp: fix typo in comment
Date: Mon, 08 Sep 2025 09:20:00 +0800 [thread overview]
Message-ID: <9529c4d417636e87691ef815e7055fe5346c4926.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250905165006.3032472-1-alok.a.tiwari@oracle.com>
Hi Alok,
> Correct a typo in af_mctp.c: "fist" -> "first".
Thanks.
Acked-by: Jeremy Kerr <jk@codeconstruct.com.au>
Cheers,
Jeremy
next prev parent reply other threads:[~2025-09-08 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 16:50 [PATCH net-next] net: mctp: fix typo in comment Alok Tiwari
2025-09-08 1:20 ` Jeremy Kerr [this message]
2025-09-09 1:00 ` patchwork-bot+netdevbpf
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=9529c4d417636e87691ef815e7055fe5346c4926.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=alok.a.tiwari@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).