From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Soumya Negi <soumya.negi97@gmail.com>,
kernel test robot <lkp@intel.com>,
Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 1/5] staging: vme_user: Replace printk() with dev_*()
Date: Fri, 20 Oct 2023 16:35:07 +0200 [thread overview]
Message-ID: <2023102058-sedate-generous-487e@gregkh> (raw)
In-Reply-To: <424a1057-894d-90ec-49ce-37aac941b497@inria.fr>
On Fri, Oct 20, 2023 at 09:50:40AM +0200, Julia Lawall wrote:
>
>
> On Fri, 20 Oct 2023, Soumya Negi wrote:
>
> > On Fri, Oct 20, 2023 at 01:09:26PM +0800, kernel test robot wrote:
> > > Hi Soumya,
> > >
> > > kernel test robot noticed the following build warnings:
> > >
> > > [auto build test WARNING on staging/staging-testing]
> > >
> > > url: https://github.com/intel-lab-lkp/linux/commits/Soumya-Negi/staging-vme_user-Replace-printk-with-dev_/20231020-095619
> > > base: staging/staging-testing
> > > patch link: https://lore.kernel.org/r/a36a0b839f9c21efe1f2df6f9272ae882fd04fb8.1697763267.git.soumya.negi97%40gmail.com
> > > patch subject: [PATCH v3 1/5] staging: vme_user: Replace printk() with dev_*()
> > > reproduce: (https://download.01.org/0day-ci/archive/20231020/202310201236.d4IEfmLQ-lkp@intel.com/reproduce)
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202310201236.d4IEfmLQ-lkp@intel.com/
> > >
> > > # many are suggestions rather than must-fix
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_slave_get', this function's name, in a string
> > > #118: FILE: drivers/staging/vme_user/vme.c:425:
> > > + dev_err(bridge->parent, "vme_slave_get not supported\n");
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_master_set', this function's name, in a string
> > > #191: FILE: drivers/staging/vme_user/vme.c:577:
> > > + dev_warn(bridge->parent, "vme_master_set not supported\n");
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_lm_set', this function's name, in a string
> > > #583: FILE: drivers/staging/vme_user/vme.c:1577:
> > > + dev_err(bridge->parent, "vme_lm_set not supported\n");
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_lm_get', this function's name, in a string
> > > #600: FILE: drivers/staging/vme_user/vme.c:1613:
> > > + dev_err(bridge->parent, "vme_lm_get not supported\n");
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_lm_attach', this function's name, in a string
> > > #617: FILE: drivers/staging/vme_user/vme.c:1650:
> > > + dev_err(bridge->parent, "vme_lm_attach not supported\n");
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_lm_detach', this function's name, in a string
> > > #634: FILE: drivers/staging/vme_user/vme.c:1683:
> > > + dev_err(bridge->parent, "vme_lm_detach not supported\n");
> > >
> > > WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'vme_slot_num', this function's name, in a string
> > > #662: FILE: drivers/staging/vme_user/vme.c:1751:
> > > + dev_warn(bridge->parent, "vme_slot_num not supported\n");
> > >
> > > --
> > > 0-DAY CI Kernel Test Service
> > > https://github.com/intel/lkp-tests/wiki
> >
> > Hi,
> >
> > There are changes being made in stages. This patch is replacing printk() to
> > dev_err() while keeping the message string unchanged. The function names
> > embedded are removed from the message strings by using __func__ in the next
> > patch of this patchset:
> >
> > "[PATCH v3 2/5] staging: vme_user: Use __func__ instead of function name"
> >
> > And the warnings go away.
> >
> > Should the tags suggested by this bot be added to [PATCH v3 2/5] in this
> > case?
>
> I think you can just ignore the bot completely in this case, because you
> already made the changes.
Agreed, this is safe to ignore, thanks.
greg k-h
next prev parent reply other threads:[~2023-10-20 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 1:55 [PATCH v3 0/5] staging: vme_user: Remove printk's & clean up log messages Soumya Negi
2023-10-20 1:55 ` [PATCH v3 1/5] staging: vme_user: Replace printk() with dev_*() Soumya Negi
2023-10-20 5:09 ` kernel test robot
2023-10-20 7:26 ` Soumya Negi
2023-10-20 7:50 ` Julia Lawall
2023-10-20 14:35 ` Greg Kroah-Hartman [this message]
2023-10-20 1:55 ` [PATCH v3 2/5] staging: vme_user: Use __func__ instead of function name Soumya Negi
2023-10-20 1:55 ` [PATCH v3 3/5] staging: vme_user: Remove printk() in find_bridge() Soumya Negi
2023-10-20 1:55 ` [PATCH v3 4/5] staging: vme_user: Remove NULL-checks Soumya Negi
2023-10-20 1:55 ` [PATCH v3 5/5] staging: vme_user: Use dev_err() in vme_check_window() Soumya Negi
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=2023102058-sedate-generous-487e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andi.shyti@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=lkp@intel.com \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=soumya.negi97@gmail.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.