From: Lu Wei <luwei32@huawei.com>
To: <vyasevich@gmail.com>, <nhorman@tuxdriver.com>,
<marcelo.leitner@gmail.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <linux-sctp@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sgarzare@redhat.com>, <jhansen@vmware.com>,
<colin.king@canonical.com>, <nslusarek@gmx.net>,
<andraprs@amazon.com>, <alex.popov@linux.com>,
<santosh.shilimkar@oracle.com>, <linux-rdma@vger.kernel.org>,
<rds-devel@oss.oracle.com>
Subject: [PATCH -next 1/3] net: rds: Fix a typo
Date: Sat, 27 Mar 2021 10:27:22 +0800 [thread overview]
Message-ID: <20210327022724.241376-2-luwei32@huawei.com> (raw)
In-Reply-To: <20210327022724.241376-1-luwei32@huawei.com>
Modify "beween" to "between" in net/rds/send.c.
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Lu Wei <luwei32@huawei.com>
---
net/rds/send.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rds/send.c b/net/rds/send.c
index 985d0b7713ac..53444397de66 100644
--- a/net/rds/send.c
+++ b/net/rds/send.c
@@ -1225,7 +1225,7 @@ int rds_sendmsg(struct socket *sock, struct msghdr *msg, size_t payload_len)
}
/* If the socket is already bound to a link local address,
* it can only send to peers on the same link. But allow
- * communicating beween link local and non-link local address.
+ * communicating between link local and non-link local address.
*/
if (scope_id != rs->rs_bound_scope_id) {
if (!scope_id) {
--
2.17.1
next prev parent reply other threads:[~2021-03-27 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 2:27 [PATCH -next 0/3] Fix some typos Lu Wei
2021-03-27 2:27 ` Lu Wei [this message]
2021-03-27 2:27 ` [PATCH -next 2/3] net: sctp: " Lu Wei
2021-03-27 2:27 ` [PATCH -next 3/3] net: vsock: Fix a typo Lu Wei
2021-03-29 1:00 ` [PATCH -next 0/3] Fix some typos 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=20210327022724.241376-2-luwei32@huawei.com \
--to=luwei32@huawei.com \
--cc=alex.popov@linux.com \
--cc=andraprs@amazon.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=jhansen@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nslusarek@gmx.net \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sgarzare@redhat.com \
--cc=vyasevich@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;
as well as URLs for NNTP newsgroup(s).