linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Florian Westphal <fw@strlen.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Miller <davem@davemloft.net>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	NetFilter <netfilter-devel@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fernando Fernandez Mancera <ffmancera@riseup.net>
Subject: Re: linux-next: build warning after merge of the netfilter-next tree
Date: Tue, 15 May 2018 12:54:22 +0200	[thread overview]
Message-ID: <CAMuHMdU0iUBbkPL5ZKxKuORnQA9ujX1J+5NLw=ft80hJh20VxQ@mail.gmail.com> (raw)
In-Reply-To: <20180508071756.grie5wln2lpo52un@breakpoint.cc>

Hi Florian,

On Tue, May 8, 2018 at 9:17 AM, Florian Westphal <fw@strlen.de> wrote:
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> On Mon, 7 May 2018 10:55:19 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> >
>> > After merging the netfilter-next tree, today's linux-next build (x86_64
>> > allmodconfig) produced this warning:
>> >
>> > ./usr/include/linux/netfilter/nf_osf.h:25: found __[us]{8,16,32,64} type without #include <linux/types.h>
>>
>> > Introduced by commit
>> >
>> >   bfb15f2a95cb ("netfilter: extract Passive OS fingerprint infrastructure from xt_osf")
>
> I'll send a fix for this, thanks for reporting.

+config NF_OSF
+       tristate 'Passive OS fingerprint infrastructure'

"There is no help available for this option."

Is this meant to be a user-visible symbol?
I noticed it is selected by NETFILTER_XT_MATCH_OSF.

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2018-05-15 10:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07  0:55 linux-next: build warning after merge of the netfilter-next tree Stephen Rothwell
2018-05-08  0:21 ` Stephen Rothwell
2018-05-08  7:17   ` Florian Westphal
2018-05-15 10:54     ` Geert Uytterhoeven [this message]
2018-05-15 17:51       ` Florian Westphal
2018-05-08  8:05   ` [PATCH nf-next] netfilter: fix fallout from xt/nf osf separation Florian Westphal
2018-05-17 11:52     ` Pablo Neira Ayuso
  -- strict thread matches above, loose matches on Subject: below --
2020-03-30  0:26 linux-next: build warning after merge of the netfilter-next tree Stephen Rothwell
2018-01-02  1:14 Stephen Rothwell
2018-01-02 15:30 ` Pablo Neira Ayuso
2017-11-07  0:02 Stephen Rothwell
2017-11-08  8:00 ` Stephen Rothwell
2017-11-08 23:40   ` Pablo Neira Ayuso
2017-11-15 22:46     ` Stephen Rothwell
2017-11-16 14:18       ` Pablo Neira Ayuso
2017-11-16 20:46         ` Stephen Rothwell
2017-03-20  0:12 Stephen Rothwell
2017-03-20  7:00 ` Reshetova, Elena
2017-03-20  8:44   ` Stephen Rothwell

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='CAMuHMdU0iUBbkPL5ZKxKuORnQA9ujX1J+5NLw=ft80hJh20VxQ@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=davem@davemloft.net \
    --cc=ffmancera@riseup.net \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).