From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] staging: r8188eu: Fix kernel-doc
Date: Mon, 6 Jun 2022 14:58:56 +0700 [thread overview]
Message-ID: <Yp2zwBqn6uDvGNWN@debian.me> (raw)
In-Reply-To: <Yp2WPrOz85/70CZx@kroah.com>
On Mon, Jun 06, 2022 at 07:53:02AM +0200, Greg KH wrote:
> On Tue, May 24, 2022 at 04:39:14PM +0800, Jiapeng Chong wrote:
> > Fix the following W=1 kernel warnings:
> >
> > drivers/staging/r8188eu/hal/rtl8188e_phycfg.c:291: warning: expecting
> > prototype for Function(). Prototype was for rtl8188e_PHY_SetRFReg()
> > instead.
> >
> > drivers/staging/r8188eu/hal/rtl8188e_phycfg.c:257: warning: expecting
> > prototype for Function(). Prototype was for rtl8188e_PHY_QueryRFReg()
> > instead.
>
> Please put build warning lines all on one line.
>
> >
> > Reported-by: Abaci Robot <abaci@linux.alibaba.com>
>
> No, gcc reported this, not a robot, right?
>
> You have read Documentation/process/researcher-guidelines.rst for how to
> properly document patches that are created by research tools like this,
> right? Please fix this commit up to follow those requirements please.
>
Hi Greg and Jiapeng,
First, IMO this is not research tool (in the sense of academic purposes),
but development bot used in corporate environment, kinda like kernel
test robot <lkp@intel.com>. When the bot reports any build warnings,
these will be followed up by developers proposing fixes.
What I see in the patch message is just "Fix this warning..." without
saying why there is the warning.
Second, gcc DOESN'T, again DOESN'T, report "expecting prototype"
warnings. These are from scripts/kernel-doc, which enabled these
warnings on W=1 build.
So the underlying problem is mismatching function name in kernel-doc
comment and actual function.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-06-06 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 8:39 [PATCH] staging: r8188eu: Fix kernel-doc Jiapeng Chong
2022-06-06 5:53 ` Greg KH
2022-06-06 7:58 ` Bagas Sanjaya [this message]
2022-06-07 11:00 ` Greg KH
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=Yp2zwBqn6uDvGNWN@debian.me \
--to=bagasdotme@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=abaci@linux.alibaba.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.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