Netdev List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [patch net-next v3 08/10] netlink: specs: devlink: add the remaining command to generate complete split_ops
Date: Sun, 22 Oct 2023 00:04:36 +0800	[thread overview]
Message-ID: <202310212326.u0Z0O9Hx-lkp@intel.com> (raw)
In-Reply-To: <20231021112711.660606-9-jiri@resnulli.us>

Hi Jiri,

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/Jiri-Pirko/genetlink-don-t-merge-dumpit-split-op-for-different-cmds-into-single-iter/20231021-192916
base:   net-next/main
patch link:    https://lore.kernel.org/r/20231021112711.660606-9-jiri%40resnulli.us
patch subject: [patch net-next v3 08/10] netlink: specs: devlink: add the remaining command to generate complete split_ops
reproduce: (https://download.01.org/0day-ci/archive/20231021/202310212326.u0Z0O9Hx-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/202310212326.u0Z0O9Hx-lkp@intel.com/

# many are suggestions rather than must-fix

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4155: FILE: tools/net/ynl/generated/devlink-user.c:1244:
+		if (type == DEVLINK_ATTR_RELOAD_STATS_ENTRY) {
+			n_reload_stats_entry++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4222: FILE: tools/net/ynl/generated/devlink-user.c:1311:
+		if (type == DEVLINK_ATTR_DPIPE_MATCH) {
+			n_dpipe_match++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4272: FILE: tools/net/ynl/generated/devlink-user.c:1361:
+		if (type == DEVLINK_ATTR_DPIPE_ACTION) {
+			n_dpipe_action++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4322: FILE: tools/net/ynl/generated/devlink-user.c:1411:
+		if (type == DEVLINK_ATTR_DPIPE_MATCH_VALUE) {
+			n_dpipe_match_value++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4372: FILE: tools/net/ynl/generated/devlink-user.c:1461:
+		if (type == DEVLINK_ATTR_DPIPE_ACTION_VALUE) {
+			n_dpipe_action_value++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4422: FILE: tools/net/ynl/generated/devlink-user.c:1511:
+		if (type == DEVLINK_ATTR_DPIPE_FIELD) {
+			n_dpipe_field++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4471: FILE: tools/net/ynl/generated/devlink-user.c:1560:
+		if (type == DEVLINK_ATTR_RESOURCE) {
+			n_resource++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4754: FILE: tools/net/ynl/generated/devlink-user.c:1843:
+		if (type == DEVLINK_ATTR_RELOAD_ACTION_INFO) {
+			n_reload_action_info++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4803: FILE: tools/net/ynl/generated/devlink-user.c:1892:
+		if (type == DEVLINK_ATTR_DPIPE_TABLE) {
+			n_dpipe_table++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4852: FILE: tools/net/ynl/generated/devlink-user.c:1941:
+		if (type == DEVLINK_ATTR_DPIPE_ENTRY) {
+			n_dpipe_entry++;
+		}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#4901: FILE: tools/net/ynl/generated/devlink-user.c:1990:
+		if (type == DEVLINK_ATTR_DPIPE_HEADER) {
+			n_dpipe_header++;
+		}

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#9828: FILE: tools/net/ynl/generated/devlink-user.h:999:
+	struct devlink_sb_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#9991: FILE: tools/net/ynl/generated/devlink-user.h:1129:
+	struct devlink_sb_pool_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#10218: FILE: tools/net/ynl/generated/devlink-user.h:1356:
+	struct devlink_sb_port_pool_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#10458: FILE: tools/net/ynl/generated/devlink-user.h:1596:
+	struct devlink_sb_tc_pool_bind_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#11435: FILE: tools/net/ynl/generated/devlink-user.h:2573:
+	struct devlink_param_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#11641: FILE: tools/net/ynl/generated/devlink-user.h:2779:
+	struct devlink_region_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#11928: FILE: tools/net/ynl/generated/devlink-user.h:3066:
+	struct devlink_region_read_rsp_dump obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#12011: FILE: tools/net/ynl/generated/devlink-user.h:3149:
+	struct devlink_port_param_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#12144: FILE: tools/net/ynl/generated/devlink-user.h:3282:
+	struct devlink_info_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#12294: FILE: tools/net/ynl/generated/devlink-user.h:3426:
+	struct devlink_health_reporter_get_rsp obj __attribute__ ((aligned (8)));

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#12719: FILE: tools/net/ynl/generated/devlink-user.h:3739:
+	struct devlink_health_reporter_dump_get_rsp_dump obj __attribute__ ((aligned (8)));

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-10-21 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 11:27 [patch net-next v3 00/10] devlink: finish conversion to generated split_ops Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 01/10] genetlink: don't merge dumpit split op for different cmds into single iter Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 02/10] tools: ynl-gen: introduce support for bitfield32 attribute type Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 03/10] tools: ynl-gen: render rsp_parse() helpers if cmd has only dump op Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 04/10] netlink: specs: devlink: remove reload-action from devlink-get cmd reply Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 05/10] netlink: specs: devlink: make dont-validate single line Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 06/10] devlink: make devlink_flash_overwrite enum named one Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 07/10] devlink: rename netlink callback to be aligned with the generated ones Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 08/10] netlink: specs: devlink: add the remaining command to generate complete split_ops Jiri Pirko
2023-10-21 16:04   ` kernel test robot [this message]
2023-10-22  9:46     ` Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 09/10] devlink: remove duplicated netlink callback prototypes Jiri Pirko
2023-10-21 11:27 ` [patch net-next v3 10/10] devlink: remove netlink small_ops Jiri Pirko
2023-10-23 20:23 ` [patch net-next v3 00/10] devlink: finish conversion to generated split_ops Jacob Keller
2023-10-23 23:50 ` patchwork-bot+netdevbpf

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=202310212326.u0Z0O9Hx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jiri@resnulli.us \
    --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