From: Ilya Dryomov <idryomov@gmail.com>
To: patchwork-bot+netdevbpf@kernel.org, Jakub Kicinski <kuba@kernel.org>
Cc: Zheng Yongjun <zhengyongjun3@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Ceph Development <ceph-devel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH net-next] libceph: Fix spelling mistakes
Date: Thu, 3 Jun 2021 22:42:26 +0200 [thread overview]
Message-ID: <CAOi1vP-wwcjS+W1o_5hA8CCgYykg=V7g3zU3yNvjSVO3wsxx5w@mail.gmail.com> (raw)
In-Reply-To: <162275220464.19203.17231827580306620053.git-patchwork-notify@kernel.org>
On Thu, Jun 3, 2021 at 10:30 PM <patchwork-bot+netdevbpf@kernel.org> wrote:
>
> Hello:
>
> This patch was applied to netdev/net-next.git (refs/heads/master):
>
> On Wed, 2 Jun 2021 14:56:35 +0800 you wrote:
> > Fix some spelling mistakes in comments:
> > enconding ==> encoding
> > ambigous ==> ambiguous
> > orignal ==> original
> > encyption ==> encryption
> >
> > Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
> >
> > [...]
>
> Here is the summary with links:
> - [net-next] libceph: Fix spelling mistakes
> https://git.kernel.org/netdev/net-next/c/dd0d91b91398
Not sure who is in charge of the bot. Jakub, perhaps you?
This patch was picked up into ceph tree yesterday and is already in
linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20210603&id=f9f9eb473076d7d1e40bfb42e626c6ae19720647
Thanks,
Ilya
prev parent reply other threads:[~2021-06-03 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 6:56 [PATCH net-next] libceph: Fix spelling mistakes Zheng Yongjun
2021-06-02 7:58 ` Ilya Dryomov
2021-06-03 20:30 ` patchwork-bot+netdevbpf
2021-06-03 20:42 ` Ilya Dryomov [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='CAOi1vP-wwcjS+W1o_5hA8CCgYykg=V7g3zU3yNvjSVO3wsxx5w@mail.gmail.com' \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=zhengyongjun3@huawei.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).