From: David Miller <davem@davemloft.net>
To: zhengyongjun3@huawei.com
Cc: jmaloy@redhat.com, ying.xue@windriver.com, kuba@kernel.org,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, hulkci@huawei.com
Subject: Re: [PATCH net-next] net: tipc: Fix spelling errors in net/tipc module
Date: Tue, 06 Apr 2021 16:45:59 -0700 (PDT) [thread overview]
Message-ID: <20210406.164559.1676626074998403447.davem@davemloft.net> (raw)
In-Reply-To: <20210406151909.298732-1-zhengyongjun3@huawei.com>
From: Zheng Yongjun <zhengyongjun3@huawei.com>
Date: Tue, 6 Apr 2021 23:19:09 +0800
> These patches fix a series of spelling errors in net/tipc module.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
This does not apply to net-next, please respin.
Thanks.
prev parent reply other threads:[~2021-04-06 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 15:19 [PATCH net-next] net: tipc: Fix spelling errors in net/tipc module Zheng Yongjun
2021-04-06 23:45 ` David Miller [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=20210406.164559.1676626074998403447.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hulkci@huawei.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
--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).