From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 9 (net/netfilter/nfnetlink_hook.c)
Date: Thu, 10 Jun 2021 00:02:53 +0200 [thread overview]
Message-ID: <20210609220253.GA7342@salvia> (raw)
In-Reply-To: <7b172e41-f483-bfc1-4f41-f92ea0b3b19d@infradead.org>
On Wed, Jun 09, 2021 at 03:00:42PM -0700, Randy Dunlap wrote:
> On 6/9/21 5:57 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20210608:
> >
>
> on i386:
>
> ../net/netfilter/nfnetlink_hook.c: In function ‘nfnl_hook_put_nft_chain_info’:
> ../net/netfilter/nfnetlink_hook.c:76:7: error: implicit declaration of function ‘nft_is_active’; did you mean ‘sev_es_active’? [-Werror=implicit-function-declaration]
> if (!nft_is_active(net, chain))
> ^~~~~~~~~~~~~
> sev_es_active
> ../net/netfilter/nfnetlink_hook.c: In function ‘nfnl_hook_entries_head’:
> ../net/netfilter/nfnetlink_hook.c:175:21: warning: unused variable ‘netdev’ [-Wunused-variable]
> struct net_device *netdev;
> ^~~~~~
> cc1: some warnings being treated as errors
>
>
> Full randconfig file is attached.
Upstream fix already in nf-next.
https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git/commit/?id=d4fb1f954fc7e2044b64b7d690400b99a6d5775c
Thanks for reporting.
next prev parent reply other threads:[~2021-06-09 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 12:57 linux-next: Tree for Jun 9 Stephen Rothwell
2021-06-09 22:00 ` linux-next: Tree for Jun 9 (net/netfilter/nfnetlink_hook.c) Randy Dunlap
2021-06-09 22:02 ` Pablo Neira Ayuso [this message]
2021-06-09 22:17 ` linux-next: Tree for Jun 9 (<linux/kvm_host.h>) Randy Dunlap
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=20210609220253.GA7342@salvia \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.