From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: Thomas Graf <tgraf@suug.ch>
Cc: shemminger@osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/7] Sync with 2.6.19 kernel header about include/linux.
Date: Tue, 05 Dec 2006 21:27:08 +0900 [thread overview]
Message-ID: <4575659C.6050904@linux-ipv6.org> (raw)
In-Reply-To: <20061205115415.GY8693@postel.suug.ch>
Thomas Graf wrote:
>>> Why are you reverting this?
>> I just update the header about include/linux without thinking.
>> Should I have to update them except fib_rules.h?
>
> The iproute2 git tree already contains patches for the
> 2.6.20 release.
OK, thanks. Can you know another patch which is already
updated to newer version except fib_fules.h, iprule.c?
Regards,
--
Masahide NAKAMURA
next prev parent reply other threads:[~2006-12-05 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 10:15 [PATCH 1/7] Sync with 2.6.19 kernel header about include/linux Masahide NAKAMURA
2006-12-05 10:42 ` Thomas Graf
2006-12-05 11:44 ` Masahide NAKAMURA
2006-12-05 11:54 ` Thomas Graf
2006-12-05 12:27 ` Masahide NAKAMURA [this message]
2006-12-05 17:34 ` 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=4575659C.6050904@linux-ipv6.org \
--to=nakam@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=tgraf@suug.ch \
/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).