From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: netdev@vger.kernel.org, usagi-users@linux-ipv6.org,
weid@np.css.fujitsu.com
Subject: (usagi-users 03790) Re: [Patch][IPv6] Fix wrong routing mechanism for Link Local IPv6 packets
Date: Tue, 30 Jan 2007 21:46:19 -0800 (PST) [thread overview]
Message-ID: <20070130.214619.74747768.davem@davemloft.net> (raw)
In-Reply-To: <20070131.144250.58478716.yoshfuji@linux-ipv6.org>
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Wed, 31 Jan 2007 14:42:50 +0900 (JST)
> In article <20070131.141408.22662891.yoshfuji@linux-ipv6.org> (at Wed, 31 Jan 2007 14:14:08 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> says:
>
> > In article <20070131.140914.105443849.yoshfuji@linux-ipv6.org> (at Wed, 31 Jan 2007 14:09:14 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> says:
> >
> > > In article <1172119906.2658.4.camel@LINE> (at Wed, 21 Feb 2007 23:51:45 -0500), weidong <weid@np.css.fujitsu.com> says:
> > >
> > > > Thanks for your patch. I think maybe we checking oif first is better,
> > > > and WARN_ON in function rt6_score_route().
> > >
> > > Please remove WARN_ON. Otherwise, I'm fine with it.
> >
> > Argh, no.... wrong.
>
> Here's updated patch, intented for net-2.6.21. Dave?
I'll integrate this after I work on some net-2.6.20
bug fixes I want to complete today.
next prev parent reply other threads:[~2007-01-31 5:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001101c744ec$5ee31720$ccb1220a@ZhaoleiSOTEC>
2007-01-31 4:11 ` [Patch][IPv6] Fix wrong routing mechanism for Link Local IPv6 packets weidong
2007-01-31 5:09 ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-31 5:14 ` (usagi-users 03788) " YOSHIFUJI Hideaki / 吉藤英明
2007-01-31 5:42 ` (usagi-users 03789) " YOSHIFUJI Hideaki / 吉藤英明
2007-01-31 5:46 ` David Miller [this message]
2007-02-05 0:59 ` David Miller
2007-01-31 4:29 ` (usagi-users 03785) " weidong
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=20070130.214619.74747768.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=usagi-users@linux-ipv6.org \
--cc=weid@np.css.fujitsu.com \
--cc=yoshfuji@linux-ipv6.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).