From: Markus Elfring <Markus.Elfring@web.de>
To: zhong jiang <zhongjiang@huawei.com>, kernel-janitors@vger.kernel.org
Cc: Anna Schumaker <anna.schumaker@netapp.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NFS: Checking the handling of patch variations
Date: Thu, 5 Sep 2019 11:00:38 +0200 [thread overview]
Message-ID: <6687a296-e656-872e-02e4-e2722383d363@web.de> (raw)
In-Reply-To: <5D7075B7.3080400@huawei.com>
>> I suggest to take another look at a similar patch.
> How to fast find out the similar patch. Search the key word doesn't work well.
This is a recurring development challenge, isn't it?
The occurrence of related update suggestions can occasionally become
more interesting.
Regards,
Markus
prev parent reply other threads:[~2019-09-05 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 6:04 [PATCH] NFS: remove the redundant check when kfree an object in nfs_netns_client_release zhong jiang
2019-09-04 15:11 ` Markus Elfring
2019-09-05 2:40 ` zhong jiang
2019-09-05 9:00 ` Markus Elfring [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=6687a296-e656-872e-02e4-e2722383d363@web.de \
--to=markus.elfring@web.de \
--cc=anna.schumaker@netapp.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=zhongjiang@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).