From: patchwork-bot+netdevbpf@kernel.org
To: Lu Wei <luwei32@huawei.com>
Cc: 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: Re: [PATCH -next 0/3] Fix some typos
Date: Mon, 29 Mar 2021 01:00:11 +0000 [thread overview]
Message-ID: <161697961124.31306.16406247961568026068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210327022724.241376-1-luwei32@huawei.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 27 Mar 2021 10:27:21 +0800 you wrote:
> Lu Wei (3):
> net: rds: Fix a typo
> net: sctp: Fix some typos
> net: vsock: Fix a typo
>
> net/rds/send.c | 2 +-
> net/sctp/sm_make_chunk.c | 2 +-
> net/sctp/socket.c | 2 +-
> net/vmw_vsock/af_vsock.c | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
Here is the summary with links:
- [-next,1/3] net: rds: Fix a typo
https://git.kernel.org/netdev/net-next/c/ebf893958c13
- [-next,2/3] net: sctp: Fix some typos
https://git.kernel.org/netdev/net-next/c/21c00a186fac
- [-next,3/3] net: vsock: Fix a typo
https://git.kernel.org/netdev/net-next/c/9195f06b2d0f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-29 1:01 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 ` [PATCH -next 1/3] net: rds: Fix a typo Lu Wei
2021-03-27 2:27 ` [PATCH -next 2/3] net: sctp: Fix some typos Lu Wei
2021-03-27 2:27 ` [PATCH -next 3/3] net: vsock: Fix a typo Lu Wei
2021-03-29 1:00 ` patchwork-bot+netdevbpf [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=161697961124.31306.16406247961568026068.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=luwei32@huawei.com \
--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).