From: Chuck Lever <chuck.lever@oracle.com>
To: Wang Hai <wanghai38@huawei.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Bruce Fields <bfields@fieldses.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] SUNRPC: remove duplicate include
Date: Wed, 19 Aug 2020 13:40:01 -0400 [thread overview]
Message-ID: <EFE54752-7DA7-465C-908B-F46B89DC3C2A@oracle.com> (raw)
In-Reply-To: <20200819024943.26850-1-wanghai38@huawei.com>
> On Aug 18, 2020, at 10:49 PM, Wang Hai <wanghai38@huawei.com> wrote:
>
> Remove linux/sunrpc/auth_gss.h which is included more than once
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Wang Hai <wanghai38@huawei.com>
I've reviewed and compile-tested this, so no objection from me.
Since this duplicate was introduced in nfsd-5.9, I can take this
for an nfsd-5.9-rc pull, if there are no other objections.
> ---
> net/sunrpc/auth_gss/trace.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/net/sunrpc/auth_gss/trace.c b/net/sunrpc/auth_gss/trace.c
> index d26036a57443..76685abba60f 100644
> --- a/net/sunrpc/auth_gss/trace.c
> +++ b/net/sunrpc/auth_gss/trace.c
> @@ -9,7 +9,6 @@
> #include <linux/sunrpc/svc_xprt.h>
> #include <linux/sunrpc/auth_gss.h>
> #include <linux/sunrpc/gss_err.h>
> -#include <linux/sunrpc/auth_gss.h>
>
> #define CREATE_TRACE_POINTS
> #include <trace/events/rpcgss.h>
> --
> 2.17.1
>
--
Chuck Lever
prev parent reply other threads:[~2020-08-19 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 2:49 Wang Hai
2020-08-19 17:40 ` Chuck Lever [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=EFE54752-7DA7-465C-908B-F46B89DC3C2A@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--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=wanghai38@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®