From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] mptcp: move pr_fmt defining to protocol.h
Date: Sat, 04 Apr 2020 17:32:59 +0800 [thread overview]
Message-ID: <202004041713.9nfGTo3l%lkp@intel.com> (raw)
In-Reply-To: <34c83a5fe561739c7b85a3c4959eb44c3155d075.1585899578.git.geliangtang@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
Hi Geliang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mptcp/export]
[also build test WARNING on linus/master v5.6 next-20200403]
[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/Geliang-Tang/mptcp-move-pr_fmt-defining-to-protocol-h/20200404-100753
base: https://github.com/multipath-tcp/mptcp_net-next.git export
config: c6x-allyesconfig (attached as .config)
compiler: c6x-elf-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=9.3.0 make.cross ARCH=c6x
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from net/mptcp/protocol.c:21:
>> net/mptcp/protocol.h:10: warning: "pr_fmt" redefined
10 | #define pr_fmt(fmt) "MPTCP: " fmt
|
In file included from include/linux/kernel.h:15,
from net/mptcp/protocol.c:7:
include/linux/printk.h:288: note: this is the location of the previous definition
288 | #define pr_fmt(fmt) fmt
|
vim +/pr_fmt +10 net/mptcp/protocol.h
9
> 10 #define pr_fmt(fmt) "MPTCP: " fmt
11
---
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: 51938 bytes --]
next prev parent reply other threads:[~2020-04-04 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 7:57 [MPTCP] [PATCH] mptcp: move pr_fmt defining to protocol.h Geliang Tang
2020-04-03 7:57 ` Geliang Tang
2020-04-04 9:32 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-03 9:14 [MPTCP] [PATCH v2] mptcp: add some missing pr_fmt defines Geliang Tang
2020-04-03 9:14 ` Geliang Tang
2020-04-03 10:29 [MPTCP] Re: [PATCH] mptcp: move pr_fmt defining to protocol.h Matthieu Baerts
2020-04-03 10:29 ` Matthieu Baerts
2020-04-03 11:41 [MPTCP] " Geliang Tang
2020-04-03 11:41 ` Geliang Tang
2020-04-03 11:49 [MPTCP] " Geliang Tang
2020-04-03 11:49 ` Geliang Tang
2020-04-03 11:57 [MPTCP] Re: [PATCH v2] mptcp: add some missing pr_fmt defines Matthieu Baerts
2020-04-03 11:57 ` Matthieu Baerts
2020-04-03 23:06 [MPTCP] " David Miller
2020-04-03 23:06 ` David Miller
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=202004041713.9nfGTo3l%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.