From: kernel test robot <lkp@intel.com>
To: Matt Johnston <matt@codeconstruct.com.au>,
linux-i3c@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH net-next v4 3/3] mctp i3c: MCTP I3C driver
Date: Sat, 7 Oct 2023 13:50:44 +0800 [thread overview]
Message-ID: <202310071339.iWeOdKQk-lkp@intel.com> (raw)
In-Reply-To: <20231004031316.725107-4-matt@codeconstruct.com.au>
Hi Matt,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Matt-Johnston/dt-bindings-i3c-Add-mctp-controller-property/20231004-111533
base: net-next/main
patch link: https://lore.kernel.org/r/20231004031316.725107-4-matt%40codeconstruct.com.au
patch subject: [PATCH net-next v4 3/3] mctp i3c: MCTP I3C driver
config: x86_64-buildonly-randconfig-005-20231007 (https://download.01.org/0day-ci/archive/20231007/202310071339.iWeOdKQk-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231007/202310071339.iWeOdKQk-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/202310071339.iWeOdKQk-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/net/mctp/mctp-i3c.c:13:0:
>> drivers/net/mctp/mctp-i3c.c:710:12: error: initializer element is not constant
I3C_CLASS(I3C_DCR_MCTP, NULL),
^
include/linux/i3c/device.h:166:10: note: in definition of macro 'I3C_CLASS'
.dcr = _dcr, \
^~~~
drivers/net/mctp/mctp-i3c.c:710:12: note: (near initialization for 'mctp_i3c_ids[0].dcr')
I3C_CLASS(I3C_DCR_MCTP, NULL),
^
include/linux/i3c/device.h:166:10: note: in definition of macro 'I3C_CLASS'
.dcr = _dcr, \
^~~~
vim +710 drivers/net/mctp/mctp-i3c.c
708
709 static const struct i3c_device_id mctp_i3c_ids[] = {
> 710 I3C_CLASS(I3C_DCR_MCTP, NULL),
711 { 0 },
712 };
713
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2023-10-07 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 3:13 [PATCH net-next v4 0/3] I3C MCTP net driver Matt Johnston
2023-10-04 3:13 ` [PATCH net-next v4 1/3] dt-bindings: i3c: Add mctp-controller property Matt Johnston
2023-10-04 3:13 ` [PATCH net-next v4 2/3] i3c: Add support for bus enumeration & notification Matt Johnston
2023-10-04 3:13 ` [PATCH net-next v4 3/3] mctp i3c: MCTP I3C driver Matt Johnston
2023-10-07 5:50 ` 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=202310071339.iWeOdKQk-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).