linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Eliminate compilation warnings for misc
Date: Mon, 29 Nov 2021 13:19:25 +0000	[thread overview]
Message-ID: <YaTTXSTiOpL1/ymL@casper.infradead.org> (raw)
In-Reply-To: <e06a86b2-1624-986c-9e97-ffac121dc240@linux.alibaba.com>

On Mon, Nov 29, 2021 at 09:06:09PM +0800, Tianjia Zhang wrote:
> Hi Randy,
> 
> On 11/17/21 7:00 AM, Randy Dunlap wrote:
> > On 11/16/21 12:06 AM, Tianjia Zhang wrote:
> > > Eliminate the following clang compilation warnings by adding or
> > > fixing function comment:
> > 
> > These are from clang?  They all appear to be from scripts/kernel-doc.
> > 
> > Can someone please clarify?
> > 
> > thanks.
> 
> Yes, compile with W=1, clang will report this warning.

No, clang has nothing to do with it.  The warnings are from kernel-doc,
not clang.  Nor gcc.

  reply	other threads:[~2021-11-29 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16  8:06 [PATCH] fs: Eliminate compilation warnings for misc Tianjia Zhang
2021-11-16 17:19 ` Matthew Wilcox
2021-11-29 13:04   ` Tianjia Zhang
2021-11-16 23:00 ` Randy Dunlap
2021-11-29 13:06   ` Tianjia Zhang
2021-11-29 13:19     ` Matthew Wilcox [this message]
2021-12-01  9:51       ` Tianjia Zhang

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=YaTTXSTiOpL1/ymL@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=rdunlap@infradead.org \
    --cc=tianjia.zhang@linux.alibaba.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).