Linux-NFS Archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev, Anna Schumaker <anna@kernel.org>
Subject: Re: [PATCH] nfsd: add missing function name to kerneldoc comment for nfsd_nl_parse_one_export
Date: Thu, 16 Apr 2026 13:09:36 -0400	[thread overview]
Message-ID: <177635936245.12505.1422177037243680976.b4-ty@oracle.com> (raw)
In-Reply-To: <20260416-nfsd-doc-v1-1-313ee1b29ff6@kernel.org>

From: Chuck Lever <chuck.lever@oracle.com>

On Thu, 16 Apr 2026 09:10:00 -0700, Jeff Layton wrote:
> Anna was seeing these warnings with a clang W=1 build:
> 
> Warning: fs/nfsd/export.c:845 Cannot find identifier on line:
> 
> @cd: cache_detail for the svc_export cache,
> Warning: fs/nfsd/export.c:846 Cannot find identifier on line:
> 
> [...]

Applied to nfsd-testing, thanks!

[1/1] nfsd: add missing function name to kerneldoc comment for nfsd_nl_parse_one_export
      (no commit info)

--
Chuck Lever <chuck.lever@oracle.com>

      reply	other threads:[~2026-04-16 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 16:10 [PATCH] nfsd: add missing function name to kerneldoc comment for nfsd_nl_parse_one_export Jeff Layton
2026-04-16 17:09 ` 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=177635936245.12505.1422177037243680976.b4-ty@oracle.com \
    --to=cel@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=neil@brown.name \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.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 read-only IMAP folder(s) and NNTP newsgroup(s).