From: kernel test robot <lkp@intel.com>
To: Michael Cheng <michael.cheng@intel.com>, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, willy@infradead.org,
michael.cheng@intel.com, casey.g.bowman@intel.com,
lucas.demarchi@intel.com, wayne.boyer@intel.com,
tvrtko.ursulin@linux.intel.com, matthew.d.roper@intel.com,
geert@linux-m68k.org
Subject: Re: [PATCH v1] Add struct folio to cacheflush.h
Date: Fri, 22 Apr 2022 22:04:49 +0800 [thread overview]
Message-ID: <202204222144.rT2z4GlF-lkp@intel.com> (raw)
In-Reply-To: <20220225201248.984169-1-michael.cheng@intel.com>
Hi Michael,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linux/master]
[cannot apply to linus/master v5.18-rc3 next-20220422]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Michael-Cheng/Add-struct-folio-to-cacheflush-h/20220226-041442
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2c271fe77d52a0555161926c232cd5bc07178b39
config: i386-debian-10.3-kselftests (https://download.01.org/0day-ci/archive/20220422/202204222144.rT2z4GlF-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/f519440dbde207a6ade2472cd2e6c32028923342
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Michael-Cheng/Add-struct-folio-to-cacheflush-h/20220226-041442
git checkout f519440dbde207a6ade2472cd2e6c32028923342
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ld: net/dccp/feat.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/input.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/minisocks.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/options.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/output.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/proto.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/timer.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/qpolicy.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ccids/ccid2.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ackvec.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ccids/ccid3.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ccids/lib/tfrc.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ccids/lib/tfrc_equation.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ccids/lib/packet_history.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/ccids/lib/loss_interval.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
ld: net/dccp/sysctl.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/dccp/ccid.o:include/linux/cacheflush.h:7: first defined here
--
>> ld: net/ipv6/ila/ila_common.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/ipv6/ila/ila_main.o:include/linux/cacheflush.h:7: first defined here
ld: net/ipv6/ila/ila_lwt.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/ipv6/ila/ila_main.o:include/linux/cacheflush.h:7: first defined here
ld: net/ipv6/ila/ila_xlat.o:include/linux/cacheflush.h:7: multiple definition of `folio'; net/ipv6/ila/ila_main.o:include/linux/cacheflush.h:7: first defined here
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-04-22 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 20:12 Michael Cheng
2022-02-25 22:18 ` kernel test robot
2022-02-25 23:50 ` kernel test robot
2022-04-22 14:04 ` kernel test robot [this message]
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=202204222144.rT2z4GlF-lkp@intel.com \
--to=lkp@intel.com \
--cc=casey.g.bowman@intel.com \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michael.cheng@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=wayne.boyer@intel.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®