From: Philip Li <philip.li@intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: kbuild test robot <lkp@intel.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
kbuild-all@lists.01.org, joe@perches.com,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
tj@kernel.org, arnd@arndb.de, sergey.senozhatsky@gmail.com,
rostedt@goodmis.org
Subject: Re: [kbuild-all] Re: [PATCH 3/4] printk: Drop pr_warning definition
Date: Sat, 30 Nov 2019 17:03:16 +0800 [thread overview]
Message-ID: <20191130090316.GA5419@intel.com> (raw)
In-Reply-To: <20191129115347.ltzif5jstfxh3h3t@pathway.suse.cz>
On Fri, Nov 29, 2019 at 12:53:47PM +0100, Petr Mladek wrote:
> On Thu 2019-11-28 15:14:36, kbuild test robot wrote:
> > Hi Kefeng,
> >
> > Thank you for the patch! Yet something to improve:
> >
> > [auto build test ERROR on wq/for-next]
> > [cannot apply to pmladek/for-next v5.4 next-20191127]
> > [if your patch is applied to the wrong git tree, please drop us a note to help
> > improve the system. BTW, we also suggest to use '--base' option to specify the
> > base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
> >
> > url: https://github.com/0day-ci/linux/commits/Kefeng-Wang/part2-kill-pr_warning-from-kernel/20191128-085343
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-next
> > config: i386-defconfig (attached as .config)
> > compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
> > reproduce:
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > All errors (new ones prefixed by >>):
> >
> > drivers/platform/x86/eeepc-laptop.c: In function 'eeepc_rfkill_hotplug':
> > >> drivers/platform/x86/eeepc-laptop.c:581:3: error: implicit declaration of function 'pr_warning'; did you mean 'acpi_warning'? [-Werror=implicit-function-declaration]
> > pr_warning("Unable to find port\n");
> > ^~~~~~~~~~
> > acpi_warning
> > cc1: some warnings being treated as errors
>
> [...]
>
> These are false positives. These pr_warning() calls have already been
> removed in mainline via a pull request from printk.git.
thanks, we will check this to improve.
>
> Best Regards.
> Petr
>
>
> tj/wq.git for-next branch is outdated.
> This branch is outdated. The
Thanks for the info Petr, we will look into this to resolve the out of
dated base. In this case, do you have any recommended base to use?
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
next prev parent reply other threads:[~2019-11-30 8:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 0:47 [PATCH 0/4] part2: kill pr_warning from kernel Kefeng Wang
2019-11-28 0:47 ` [PATCH 1/4] workqueue: Use pr_warn instead of pr_warning Kefeng Wang
2019-12-02 18:00 ` Tejun Heo
2019-11-28 0:47 ` [PATCH 2/4] staging: isdn: gigaset: " Kefeng Wang
2019-11-29 11:49 ` Petr Mladek
2019-11-28 0:47 ` [PATCH 3/4] printk: Drop pr_warning definition Kefeng Wang
2019-11-28 7:14 ` kbuild test robot
2019-11-29 11:53 ` Petr Mladek
2019-11-30 9:03 ` Philip Li [this message]
2019-12-03 9:15 ` [kbuild-all] " Petr Mladek
2019-11-28 0:47 ` [PATCH 4/4] checkpatch: Drop pr_warning check Kefeng Wang
2019-11-28 1:05 ` Joe Perches
2019-11-29 11:58 ` [PATCH 0/4] part2: kill pr_warning from kernel Petr Mladek
2019-11-29 12:56 ` Kefeng Wang
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=20191130090316.GA5419@intel.com \
--to=philip.li@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@kernel.org \
--cc=wangkefeng.wang@huawei.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