From: kernel test robot <lkp@intel.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: net/bridge/br_private.h:901 br_multicast_rport_from_node_skb() warn: inconsistent indenting
Date: Thu, 10 Feb 2022 10:53:16 +0800 [thread overview]
Message-ID: <202202101038.9QptdYTn-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f4bc5bbb5fef3cf421ba3485d6d383c27ec473ed
commit: 9632233e7de8da43711bb7cd3e054af32fedcc38 net: bridge: multicast: factor out port multicast context
date: 7 months ago
config: openrisc-randconfig-m031-20220210 (https://download.01.org/0day-ci/archive/20220210/202202101038.9QptdYTn-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
New smatch warnings:
net/bridge/br_private.h:901 br_multicast_rport_from_node_skb() warn: inconsistent indenting
Old smatch warnings:
net/bridge/br_forward.c:317 br_multicast_flood() error: we previously assumed 'p' could be null (see line 293)
vim +901 net/bridge/br_private.h
890
891 static inline struct net_bridge_port *
892 br_multicast_rport_from_node_skb(struct hlist_node *rp, struct sk_buff *skb) {
893 struct net_bridge_mcast_port *mctx;
894
895 #if IS_ENABLED(CONFIG_IPV6)
896 if (skb->protocol == htons(ETH_P_IPV6))
897 mctx = hlist_entry_safe(rp, struct net_bridge_mcast_port,
898 ip6_rlist);
899 else
900 #endif
> 901 mctx = hlist_entry_safe(rp, struct net_bridge_mcast_port,
902 ip4_rlist);
903
904 if (mctx)
905 return mctx->port;
906 else
907 return NULL;
908 }
909
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-02-10 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 2:53 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 22:13 kernel test robot
2022-05-28 13:10 kernel test robot
2022-02-10 22:39 kernel test robot
2021-11-28 0:33 kernel test robot
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=202202101038.9QptdYTn-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikolay@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
all inboxes | Powered by JetHome®