From: kernel test robot <lkp@intel.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
kuba@kernel.org, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, mkl@pengutronix.de, davem@davemloft.net,
linux-can@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>
Subject: Re: [PATCH net-next v2 1/2] can-isotp: implement cleanups / improvements from review
Date: Mon, 12 Oct 2020 01:59:17 +0800 [thread overview]
Message-ID: <202010120155.GKRCEMOp-lkp@intel.com> (raw)
In-Reply-To: <20201011092408.1766-1-socketcan@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
Hi Oliver,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Oliver-Hartkopp/can-isotp-implement-cleanups-improvements-from-review/20201012-000055
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git df41c19abbeaae6e24c8e31cff5fdb48632be380
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/693c9b4e8c5710e7b536ec9d6a969a7d7343a100
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Oliver-Hartkopp/can-isotp-implement-cleanups-improvements-from-review/20201012-000055
git checkout 693c9b4e8c5710e7b536ec9d6a969a7d7343a100
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> net/can/isotp.c:82: warning: "pr_fmt" redefined
82 | #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
In file included from include/linux/kernel.h:15,
from include/linux/list.h:9,
from include/linux/module.h:12,
from net/can/isotp.c:56:
include/linux/printk.h:297: note: this is the location of the previous definition
297 | #define pr_fmt(fmt) fmt
|
vim +/pr_fmt +82 net/can/isotp.c
81
> 82 #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
83
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65141 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH net-next v2 1/2] can-isotp: implement cleanups / improvements from review
Date: Mon, 12 Oct 2020 01:59:17 +0800 [thread overview]
Message-ID: <202010120155.GKRCEMOp-lkp@intel.com> (raw)
In-Reply-To: <20201011092408.1766-1-socketcan@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
Hi Oliver,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Oliver-Hartkopp/can-isotp-implement-cleanups-improvements-from-review/20201012-000055
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git df41c19abbeaae6e24c8e31cff5fdb48632be380
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/693c9b4e8c5710e7b536ec9d6a969a7d7343a100
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Oliver-Hartkopp/can-isotp-implement-cleanups-improvements-from-review/20201012-000055
git checkout 693c9b4e8c5710e7b536ec9d6a969a7d7343a100
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> net/can/isotp.c:82: warning: "pr_fmt" redefined
82 | #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
In file included from include/linux/kernel.h:15,
from include/linux/list.h:9,
from include/linux/module.h:12,
from net/can/isotp.c:56:
include/linux/printk.h:297: note: this is the location of the previous definition
297 | #define pr_fmt(fmt) fmt
|
vim +/pr_fmt +82 net/can/isotp.c
81
> 82 #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
83
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65141 bytes --]
next prev parent reply other threads:[~2020-10-11 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 9:24 [PATCH net-next v2 1/2] can-isotp: implement cleanups / improvements from review Oliver Hartkopp
2020-10-11 9:24 ` [PATCH net-next v2 2/2] can: remove obsolete version strings Oliver Hartkopp
2020-10-11 15:44 ` [PATCH net-next v2 1/2] can-isotp: implement cleanups / improvements from review Jakub Kicinski
2020-10-12 7:41 ` Oliver Hartkopp
2020-10-11 15:45 ` Jakub Kicinski
2020-10-11 17:59 ` kernel test robot [this message]
2020-10-11 17:59 ` kernel test robot
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=202010120155.GKRCEMOp-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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.