All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-12-07
Date: Sat, 12 Dec 2015 09:53:02 +0100	[thread overview]
Message-ID: <1449910382.2234.9.camel@embedded.rocks> (raw)
In-Reply-To: <20151208180201.GP4188@free.fr>

Dear Yann,

On Di, 2015-12-08 at 19:02 +0100, Yann E. MORIN wrote:
> Peter, Thomas, All,
> 
> > ???????????????arptables-0.0.4 | 4 
> 
> Patch available, but not sure I understand it fully:
> ????https://patchwork.ozlabs.org/patch/551152/
> 

Let me explain...

To avoid the linux/netinet header issues (linux/netfilter implicitly
includes linux/in), the patch declares the needed ?NF_* macros and the
struct xt_classify_target_info from the linux headers in a __KERNEL__
ifdef/else condition. It's done this way to be aligned with who it's
done already in the upstream sources.

Best regards
J?rg Krause

  reply	other threads:[~2015-12-12  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-12-07 Thomas Petazzoni
2015-12-08 18:02 ` Yann E. MORIN
2015-12-12  8:53   ` Jörg Krause [this message]
2016-01-09 14:35 ` Erico Nunes

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=1449910382.2234.9.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=buildroot@busybox.net \
    /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.