From: Pablo Neira Ayuso <pablo@netfilter.org>
To: David Miller <davem@davemloft.net>
Cc: jengelh@medozas.de, lists@sterenborg.info,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] libmnl 1.0.0 release
Date: Tue, 21 Dec 2010 21:31:20 +0100 [thread overview]
Message-ID: <4D110E98.5080002@netfilter.org> (raw)
In-Reply-To: <20101221.122225.39203217.davem@davemloft.net>
On 21/12/10 21:22, David Miller wrote:
> From: Pablo Neira Ayuso <pablo@netfilter.org>
> Date: Tue, 21 Dec 2010 21:19:40 +0100
>
>> I think that this approach (see patch) is safe to fix this problem.
>
> This is fine for now, but really you should have a copy of the
> headers in your tree.
>
> It's the only way to sanely control the build in all possible
> scenerios. The kernel headers are just too large of a variable
> for things like this.
I was thinking on the overhead that this adds since we have to keep in
sync kernel and library header files. If there's some new feature in the
kernel, you'll have to wait until the new stuff in included in the
libmnl header.
But this is indeed a problem since people will report compilation problems.
I'll make a patch to add them.
next prev parent reply other threads:[~2010-12-21 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 14:20 [ANNOUNCE] libmnl 1.0.0 release Pablo Neira Ayuso
2010-12-18 5:23 ` Rob Sterenborg (lists)
2010-12-18 12:40 ` Pablo Neira Ayuso
2010-12-18 12:53 ` Pablo Neira Ayuso
2010-12-18 15:35 ` Jan Engelhardt
2010-12-21 20:19 ` Pablo Neira Ayuso
2010-12-21 20:22 ` David Miller
2010-12-21 20:31 ` Pablo Neira Ayuso [this message]
2010-12-22 19:52 ` 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=4D110E98.5080002@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=lists@sterenborg.info \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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).