From: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCHv2] ebtables: Cache a copy of the v3.16 kernel headers in the ebtables tree
Date: Thu, 26 Feb 2015 22:45:46 +0000 [thread overview]
Message-ID: <54EFA21A.5090507@codethink.co.uk> (raw)
In-Reply-To: <20150226193054.GA5142@salvia>
On 26/02/15 19:30, Pablo Neira Ayuso wrote:
> On Thu, Feb 26, 2015 at 04:37:56PM +0000, Pedro Alvarez wrote:
>>
>> I decided to go for 2, and here is the patch:
>
> Yes, we have to go 2 as we did in iptables.
>
>> Repo: git://git.baserock.org/delta/ebtables.git
>> Branch: baserock/pedroalvarez/ebt_ulog-fix
>> Sha1: 13747a56890cc710b2b4d420edc03a6c2714f40e
>>
>> NOTE: I didn't want to send a diff, since it would be big and nonsense, but I
>> can do that if needed.
>
> OK, but it should be sufficient to include netfilter_bridge headers
> for each supported extension, including types.h and filter.h as we do
> in iptables.
Hi Pablo, thanks for taking a look at my patch.
Yeah, you are right, here is the second version of the patch [1]
following your suggestion.
Repo: git://git.baserock.org/delta/ebtables.git
Branch: baserock/pedroalvarez/ebt_ulog-fix-v2
Sha1: 04d387f29184907dd61f7e6b23b0dd9ef3913c50
[1]:
http://git.baserock.org/cgi-bin/cgit.cgi/delta/ebtables.git/commit/?h=baserock/pedroalvarez/ebt_ulog-fix-v2&id=04d387f29184907dd61f7e6b23b0dd9ef3913c50
--
Pedro
next prev parent reply other threads:[~2015-02-26 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 16:37 [PATCH] ebtables: Cache a copy of the v3.16 kernel headers in the ebtables tree Pedro Alvarez
2015-02-26 19:30 ` Pablo Neira Ayuso
2015-02-26 22:45 ` Pedro Alvarez [this message]
2015-02-27 11:23 ` [PATCHv2] " Pablo Neira Ayuso
2015-02-27 11:54 ` [PATCHv3] ebtables: Add kernel headers needed from v3.16 Pedro Alvarez
2015-02-27 11:54 ` [PATCH] " Pedro Alvarez
2015-03-02 11:13 ` Pablo Neira Ayuso
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=54EFA21A.5090507@codethink.co.uk \
--to=pedro.alvarez@codethink.co.uk \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).