From: kernel test robot <lkp@intel.com>
To: Ma Ke <make_ruc2021@163.com>,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Ma Ke <make_ruc2021@163.com>
Subject: Re: [PATCH] net: sched: hfsc: dont intepret cls results when asked to drop
Date: Sat, 16 Sep 2023 00:27:51 +0800 [thread overview]
Message-ID: <202309160007.7615P5Df-lkp@intel.com> (raw)
In-Reply-To: <20230915134408.3410595-1-make_ruc2021@163.com>
Hi Ma,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
[also build test WARNING on net/main linus/master v6.6-rc1 next-20230915]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ma-Ke/net-sched-hfsc-dont-intepret-cls-results-when-asked-to-drop/20230915-214635
base: net-next/main
patch link: https://lore.kernel.org/r/20230915134408.3410595-1-make_ruc2021%40163.com
patch subject: [PATCH] net: sched: hfsc: dont intepret cls results when asked to drop
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20230916/202309160007.7615P5Df-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230916/202309160007.7615P5Df-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/202309160007.7615P5Df-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/compiler_types.h:80,
from <command-line>:
net/sched/sch_hfsc.c: In function 'hfsc_classify':
>> include/linux/compiler_attributes.h:227:41: warning: attribute 'fallthrough' not preceding a case label or default label
227 | # define fallthrough __attribute__((__fallthrough__))
| ^~~~~~~~~~~~~
net/sched/sch_hfsc.c:1146:25: note: in expansion of macro 'fallthrough'
1146 | fallthrough;
| ^~~~~~~~~~~
vim +/fallthrough +227 include/linux/compiler_attributes.h
294f69e662d157 Joe Perches 2019-10-05 214
294f69e662d157 Joe Perches 2019-10-05 215 /*
294f69e662d157 Joe Perches 2019-10-05 216 * Add the pseudo keyword 'fallthrough' so case statement blocks
294f69e662d157 Joe Perches 2019-10-05 217 * must end with any of these keywords:
294f69e662d157 Joe Perches 2019-10-05 218 * break;
294f69e662d157 Joe Perches 2019-10-05 219 * fallthrough;
ca0760e7d79e2b Wei Ming Chen 2021-05-06 220 * continue;
294f69e662d157 Joe Perches 2019-10-05 221 * goto <label>;
294f69e662d157 Joe Perches 2019-10-05 222 * return [expression];
294f69e662d157 Joe Perches 2019-10-05 223 *
294f69e662d157 Joe Perches 2019-10-05 224 * gcc: https://gcc.gnu.org/onlinedocs/gcc/Statement-Attributes.html#Statement-Attributes
294f69e662d157 Joe Perches 2019-10-05 225 */
294f69e662d157 Joe Perches 2019-10-05 226 #if __has_attribute(__fallthrough__)
294f69e662d157 Joe Perches 2019-10-05 @227 # define fallthrough __attribute__((__fallthrough__))
294f69e662d157 Joe Perches 2019-10-05 228 #else
294f69e662d157 Joe Perches 2019-10-05 229 # define fallthrough do {} while (0) /* fallthrough */
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 230 #endif
a3f8a30f3f0079 Miguel Ojeda 2018-08-30 231
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-15 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 13:44 [PATCH] net: sched: hfsc: dont intepret cls results when asked to drop Ma Ke
2023-09-15 16:27 ` kernel test robot [this message]
2023-09-16 12:03 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 12:18 Ma Ke
2023-09-15 12:57 ` Eric Dumazet
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=202309160007.7615P5Df-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make_ruc2021@163.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@gmail.com \
/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