From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: Stephen Hemminger <shemminger@osdl.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Add nl_open to libnetlink
Date: Wed, 7 Jul 2004 15:56:02 +0900 [thread overview]
Message-ID: <20040707155602.4698121a@localhost> (raw)
In-Reply-To: <20040707140533.41c66c03@localhost>
Hello Stephen and Herbert,
> > > On Sat, 3 Jul 2004 19:46:32 +1000
> > > Herbert Xu <herbert@gondor.apana.org.au> wrote:
> > >
> > > > I'm in the process of writing two new modules fo ip(8), ippolicy and
> > > > ipstate which will be a NETLINK based replacement for setkey.
> > > >
> > > > In order to do so, I need to get libnetlink to speak the XFRM protocol.
> > > > Thus I've added a new nl_open function which allows the protocol to
> > > > be specified.
> > >
> > > I agree with it.
> > >
> > > Anyway, I have code for ip(8) for similar reason.
I've updated the patch and it can build with 2.6.7 kernel headers.
Can you check it?
http://www.linux-ipv6.org/~nakam/ipxfrm-20040707_2.diff
--
Masahide NAKAMURA
next prev parent reply other threads:[~2004-07-07 6:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 9:46 [PATCH] Add nl_open to libnetlink Herbert Xu
2004-07-05 7:05 ` Masahide NAKAMURA
2004-07-05 8:07 ` Herbert Xu
2004-07-06 21:05 ` Stephen Hemminger
2004-07-07 4:09 ` Masahide NAKAMURA
2004-07-07 5:05 ` Masahide NAKAMURA
2004-07-07 6:56 ` Masahide NAKAMURA [this message]
2004-07-07 11:03 ` Herbert Xu
2004-07-09 3:51 ` Masahide NAKAMURA
2004-07-15 6:02 ` [PATCH 1/3] iproute2 and xfrm Masahide NAKAMURA
2004-07-16 22:22 ` Stephen Hemminger
[not found] ` <20040714174233.2fc7dbc2@localhost>
2004-07-15 6:02 ` [PATCH 2/3] " Masahide NAKAMURA
2004-07-16 23:05 ` Herbert Xu
[not found] ` <20040714174637.0ce79ae1@localhost>
2004-07-15 6:02 ` [PATCH 3/3] " Masahide NAKAMURA
2004-07-07 18:08 ` [PATCH] Add nl_open to libnetlink Stephen Hemminger
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=20040707155602.4698121a@localhost \
--to=nakam@linux-ipv6.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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 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.