From: kernel test robot <lkp@intel.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH net-next v5 1/2] net: dsa: Use conduit and user terms
Date: Wed, 18 Oct 2023 09:12:05 +0800 [thread overview]
Message-ID: <202310180907.RbYMqtyd-lkp@intel.com> (raw)
In-Reply-To: <20231017233536.426704-2-florian.fainelli@broadcom.com>
Hi Florian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Florian-Fainelli/net-dsa-Use-conduit-and-user-terms/20231018-073644
base: net-next/main
patch link: https://lore.kernel.org/r/20231017233536.426704-2-florian.fainelli%40broadcom.com
patch subject: [PATCH net-next v5 1/2] net: dsa: Use conduit and user terms
reproduce: (https://download.01.org/0day-ci/archive/20231018/202310180907.RbYMqtyd-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/202310180907.RbYMqtyd-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:SPLIT_STRING: quoted string split across lines
#4682: FILE: net/dsa/tag_sja1105.c:399:
"Expected meta frame, is %12llx "
+ "in the DSA conduit multicast filter?\n",
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-18 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 23:35 [PATCH net-next v5 0/2] Switch DSA to inclusive terminology Florian Fainelli
2023-10-17 23:35 ` [PATCH net-next v5 1/2] net: dsa: Use conduit and user terms Florian Fainelli
2023-10-18 1:12 ` kernel test robot [this message]
2023-10-17 23:35 ` [PATCH net-next v5 2/2] net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT Florian Fainelli
2023-10-18 15:56 ` Simon Horman
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=202310180907.RbYMqtyd-lkp@intel.com \
--to=lkp@intel.com \
--cc=florian.fainelli@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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 NNTP newsgroup(s).