From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: 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: Wed, 9 Jun 2021 15:00:42 -0700 [thread overview]
Message-ID: <7b172e41-f483-bfc1-4f41-f92ea0b3b19d@infradead.org> (raw)
In-Reply-To: <20210609225703.56bfcc12@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
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.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r9876.gz --]
[-- Type: application/gzip, Size: 44401 bytes --]
next prev parent reply other threads:[~2021-06-09 22:00 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 ` Randy Dunlap [this message]
2021-06-09 22:02 ` linux-next: Tree for Jun 9 (net/netfilter/nfnetlink_hook.c) Pablo Neira Ayuso
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=7b172e41-f483-bfc1-4f41-f92ea0b3b19d@infradead.org \
--to=rdunlap@infradead.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=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 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).