From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Yueh-Shun Li <shamrocklee@posteo.net>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S . Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@kernel.org>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-scsi@vger.kernel.org,
mptcp@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] RDMA/rxe: fix comment typo
Date: Thu, 22 Jun 2023 13:27:34 +0800 [thread overview]
Message-ID: <f6670c07-e74c-5a08-aca9-4fe9b0df1b6c@linux.dev> (raw)
In-Reply-To: <20230622012627.15050-2-shamrocklee@posteo.net>
在 2023/6/22 9:26, Yueh-Shun Li 写道:
> Spell "retransmitting" properly.
>
> Found by searching for keyword "tranm".
>
> Signed-off-by: Yueh-Shun Li <shamrocklee@posteo.net>
Thanks.
Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
Zhu Yanjun
> ---
> drivers/infiniband/sw/rxe/rxe_verbs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.h b/drivers/infiniband/sw/rxe/rxe_verbs.h
> index 26a20f088692..aca0f4c7a5cd 100644
> --- a/drivers/infiniband/sw/rxe/rxe_verbs.h
> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.h
> @@ -237,7 +237,7 @@ struct rxe_qp {
> atomic_t skb_out;
> int need_req_skb;
>
> - /* Timer for retranmitting packet when ACKs have been lost. RC
> + /* Timer for retransmitting packet when ACKs have been lost. RC
> * only. The requester sets it when it is not already
> * started. The responder resets it whenever an ack is
> * received.
next prev parent reply other threads:[~2023-06-22 5:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 1:26 [PATCH 0/8] Fix comment typos about "transmit" Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 1/8] RDMA/rxe: fix comment typo Yueh-Shun Li
2023-06-22 5:27 ` Zhu Yanjun [this message]
2023-06-22 1:26 ` [PATCH 2/8] i40e, xsk: " Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 3/8] zd1211rw: " Yueh-Shun Li
2023-07-25 14:47 ` [3/8] wifi: zd1211rw: fix typo "tranmits" Kalle Valo
2023-06-22 1:26 ` [PATCH 4/8] scsi: fix comment typo Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 5/8] tcp: " Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 6/8] net/tls: " Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 7/8] selftests: mptcp: connect: " Yueh-Shun Li
2023-06-22 8:19 ` Matthieu Baerts
2023-06-22 1:26 ` [PATCH 8/8] scripts/spelling.txt: Add "transmit" patterns Yueh-Shun Li
2023-06-22 2:09 ` Randy Dunlap
2023-06-23 2:50 ` [PATCH 0/8] Fix comment typos about "transmit" patchwork-bot+netdevbpf
2023-06-23 8:51 ` Yueh-Shun Li
2023-06-23 9:19 ` Matthieu Baerts
2023-06-23 10:36 ` Johannes Berg
2023-06-23 15:12 ` Jakub Kicinski
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=f6670c07-e74c-5a08-aca9-4fe9b0df1b6c@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=anthony.l.nguyen@intel.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shamrocklee@posteo.net \
/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).