From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Prashant Malani <pmalani@chromium.org>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev, robbarnes@google.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] platform/chrome: cros_ec_debugfs: fix kernel-doc warning
Date: Wed, 12 Apr 2023 10:48:48 +0800 [thread overview]
Message-ID: <ZDYcENIWeBgnQQ29@google.com> (raw)
In-Reply-To: <CACeCKaduOqLwGsGLEVzdG2hDNq8=07a_V-uGLZWT0f3+Wb603Q@mail.gmail.com>
On Tue, Apr 11, 2023 at 10:38:15AM -0700, Prashant Malani wrote:
> On Mon, Apr 10, 2023 at 10:33 PM Tzung-Bi Shih <tzungbi@kernel.org> wrote:
> >
> > Fix the following kernel-doc warning:
> >
> > $ ./scripts/kernel-doc -none drivers/platform/chrome/*
> > [...]
> > warning: This comment starts with '/**', but isn't a kernel-doc comment.
> >
> > Fixes: 14bb09b32f43 ("platform/chrome: cros_ec: Separate logic for getting panic info")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
> > ---
> > I should put it in my checklist in the future before pushing patches to
> > for-next.
>
> Can this be added to kernelci?
I'm afraid not; build tests performed by KernelCI only for its tests. 0-day
performs better on such kind of static checks.
next prev parent reply other threads:[~2023-04-12 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 5:33 [PATCH] platform/chrome: cros_ec_debugfs: fix kernel-doc warning Tzung-Bi Shih
2023-04-11 6:01 ` Benson Leung
2023-04-11 8:40 ` patchwork-bot+chrome-platform
2023-04-11 17:38 ` Prashant Malani
2023-04-12 2:48 ` Tzung-Bi Shih [this message]
2023-04-12 2:40 ` patchwork-bot+chrome-platform
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=ZDYcENIWeBgnQQ29@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=lkp@intel.com \
--cc=pmalani@chromium.org \
--cc=robbarnes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.