From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: takamiya@po.ntts.co.jp, anttit@tcs.hut.fi, vnuorval@tcs.hut.fi,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/7][IP] IProute2 ip command updates
Date: Tue, 28 Nov 2006 12:19:39 +0900 [thread overview]
Message-ID: <456BAACB.8040508@linux-ipv6.org> (raw)
In-Reply-To: <20061127101255.4aee9bcd@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> Plan is to put out new iproute2 release after 2.6.19 final
OK.
As you know, netlink related interface is changed at 2.6.19.
I have another patches for iproute2 (libnetlink fix and Mobile
IPv6 support). Those are depends on 2.6.19 headers.
So this time I'd like to know when to update your tree's kernel headers, too.
To use this chance to test with your tree, can I send my patches with the
header update to 2.6.19-rcX in advance (updating headers by you is also fine
with me), or just wait till 2.6.19 final release is done?
Regards,
--
Masahide NAKAMURA
prev parent reply other threads:[~2006-11-28 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 3:31 [PATCH 0/7][IP] IProute2 ip command updates Masahide NAKAMURA
2006-11-27 18:12 ` Stephen Hemminger
2006-11-28 3:19 ` Masahide NAKAMURA [this message]
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=456BAACB.8040508@linux-ipv6.org \
--to=nakam@linux-ipv6.org \
--cc=anttit@tcs.hut.fi \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=takamiya@po.ntts.co.jp \
--cc=vnuorval@tcs.hut.fi \
/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).