From: "bfields@fieldses.org" <bfields@fieldses.org>
To: zhengyongjun <zhengyongjun3@huawei.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"trond.myklebust@hammerspace.com"
<trond.myklebust@hammerspace.com>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: 答复: [PATCH net-next] xprtrdma: Fix spelling mistakes
Date: Tue, 1 Jun 2021 10:21:19 -0400 [thread overview]
Message-ID: <20210601142119.GB5320@fieldses.org> (raw)
In-Reply-To: <6b737fb5440d4fe3a53a163624d9cbf8@huawei.com>
On Tue, Jun 01, 2021 at 06:34:04AM +0000, zhengyongjun wrote:
> Should I remove net-next tag and send patch v2? Waiting for your suggest :)
Applied for 5.14, no need to resend anything.--b.
>
> -----邮件原件-----
> 发件人: Jakub Kicinski [mailto:kuba@kernel.org]
> 发送时间: 2021年6月1日 13:27
> 收件人: zhengyongjun <zhengyongjun3@huawei.com>
> 抄送: trond.myklebust@hammerspace.com; anna.schumaker@netapp.com; davem@davemloft.net; linux-nfs@vger.kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org; bfields@fieldses.org; chuck.lever@oracle.com
> 主题: Re: [PATCH net-next] xprtrdma: Fix spelling mistakes
>
> On Mon, 31 May 2021 14:36:40 +0800 Zheng Yongjun wrote:
> > Fix some spelling mistakes in comments:
> > succes ==> success
> >
> > Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
>
> This should not have been tagged for net-next, leaving it to Trond.
prev parent reply other threads:[~2021-06-01 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 6:36 Zheng Yongjun
2021-06-01 5:27 ` Jakub Kicinski
2021-06-01 6:34 ` 答复: " zhengyongjun
2021-06-01 14:21 ` bfields [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=20210601142119.GB5320@fieldses.org \
--to=bfields@fieldses.org \
--cc=anna.schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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
all inboxes | Powered by JetHome®