From: kernel test robot <lkp@intel.com>
To: Yevgeny Kliteynik <kliteyn@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Saeed Mahameed <saeedm@nvidia.com>,
Alex Vesker <valex@nvidia.com>
Subject: drivers/net/ethernet/mellanox/mlx5/core/steering/dr_ste_v1.c:855 dr_ste_v1_build_src_gvmi_qpn_tag() warn: inconsistent indenting
Date: Sat, 24 Jul 2021 05:11:07 +0800 [thread overview]
Message-ID: <202107240500.nTB6GF7J-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1d597682d3e669ec7021aa33d088ed3d136a5149
commit: 10b69418641062b4dc7fabe3c6f2e12432ec6987 net/mlx5: DR, Add HW STEv1 match logic
date: 6 months ago
config: x86_64-randconfig-m001-20210723 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
smatch warnings:
drivers/net/ethernet/mellanox/mlx5/core/steering/dr_ste_v1.c:855 dr_ste_v1_build_src_gvmi_qpn_tag() warn: inconsistent indenting
vim +855 drivers/net/ethernet/mellanox/mlx5/core/steering/dr_ste_v1.c
832
833 static int dr_ste_v1_build_src_gvmi_qpn_tag(struct mlx5dr_match_param *value,
834 struct mlx5dr_ste_build *sb,
835 u8 *tag)
836 {
837 struct mlx5dr_match_misc *misc = &value->misc;
838 struct mlx5dr_cmd_vport_cap *vport_cap;
839 struct mlx5dr_domain *dmn = sb->dmn;
840 struct mlx5dr_cmd_caps *caps;
841 u8 *bit_mask = sb->bit_mask;
842
843 DR_STE_SET_TAG(src_gvmi_qp_v1, tag, source_qp, misc, source_sqn);
844
845 if (sb->vhca_id_valid) {
846 /* Find port GVMI based on the eswitch_owner_vhca_id */
847 if (misc->source_eswitch_owner_vhca_id == dmn->info.caps.gvmi)
848 caps = &dmn->info.caps;
849 else if (dmn->peer_dmn && (misc->source_eswitch_owner_vhca_id ==
850 dmn->peer_dmn->info.caps.gvmi))
851 caps = &dmn->peer_dmn->info.caps;
852 else
853 return -EINVAL;
854
> 855 misc->source_eswitch_owner_vhca_id = 0;
856 } else {
857 caps = &dmn->info.caps;
858 }
859
860 if (!MLX5_GET(ste_src_gvmi_qp_v1, bit_mask, source_gvmi))
861 return 0;
862
863 vport_cap = mlx5dr_get_vport_cap(caps, misc->source_port);
864 if (!vport_cap) {
865 mlx5dr_err(dmn, "Vport 0x%x is disabled or invalid\n",
866 misc->source_port);
867 return -EINVAL;
868 }
869
870 if (vport_cap->vport_gvmi)
871 MLX5_SET(ste_src_gvmi_qp_v1, tag, source_gvmi, vport_cap->vport_gvmi);
872
873 misc->source_port = 0;
874 return 0;
875 }
876
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39521 bytes --]
reply other threads:[~2021-07-23 21:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202107240500.nTB6GF7J-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kliteyn@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=valex@nvidia.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;
as well as URLs for NNTP newsgroup(s).