From: Pablo Neira Ayuso <pablo@netfilter.org>
To: kernel test robot <lkp@intel.com>
Cc: Florian Westphal <fw@strlen.de>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: net/netfilter/nft_set_rbtree.c:636:33: warning: variable 'nft_net' set but not used
Date: Fri, 3 Nov 2023 10:46:34 +0100 [thread overview]
Message-ID: <ZUTBegMOO36wC4mH@calendula> (raw)
In-Reply-To: <202311031627.Kx0hfrUu-lkp@intel.com>
On Fri, Nov 03, 2023 at 04:40:55PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 8f6f76a6a29f36d2f3e4510d0bde5046672f6924
> commit: 7d259f021aaa78904b6c836d975e8e00d83a182a netfilter: nft_set_rbtree: prefer sync gc to async worker
> date: 10 days ago
> config: s390-defconfig (https://download.01.org/0day-ci/archive/20231103/202311031627.Kx0hfrUu-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231103/202311031627.Kx0hfrUu-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/202311031627.Kx0hfrUu-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> net/netfilter/nft_set_rbtree.c: In function 'nft_rbtree_gc':
> >> net/netfilter/nft_set_rbtree.c:636:33: warning: variable 'nft_net' set but not used [-Wunused-but-set-variable]
> 636 | struct nftables_pernet *nft_net;
> | ^~~~~~~
Fix is here.
It is missing Fixes: tag though.
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20231101013351.55902-1-yang.lee@linux.alibaba.com/
prev parent reply other threads:[~2023-11-03 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 8:40 net/netfilter/nft_set_rbtree.c:636:33: warning: variable 'nft_net' set but not used kernel test robot
2023-11-03 9:46 ` Pablo Neira Ayuso [this message]
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=ZUTBegMOO36wC4mH@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.