From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: robert.olsson@data.slu.se, netdev@vger.kernel.org, joonwpark81@gmail.com
Subject: Re: [PATCHv2 2.6.24] fib_trie: apply fixes from fib_hash
Date: Mon, 28 Jan 2008 21:18:22 -0800 (PST) [thread overview]
Message-ID: <20080128.211822.46715588.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0801261441470.7864@u.domain.uli>
From: Julian Anastasov <ja@ssi.bg>
Date: Sat, 26 Jan 2008 14:44:36 +0200 (EET)
>
> Update fib_trie with some fib_hash fixes:
> - check for duplicate alternative routes for prefix+tos+priority when
> replacing route
> - properly insert by matching tos together with priority
> - fix alias walking to use list_for_each_entry_continue for insertion
> and deletion when fa_head is not NULL
> - copy state from fa to new_fa on replace (not a problem for now)
> - additionally, avoid replacement without error if new route is same,
> as Joonwoo Park suggests.
>
> Signed-off-by: Julian Anastasov <ja@ssi.bg>
Also applied, thanks a lot.
prev parent reply other threads:[~2008-01-29 5:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 12:44 [PATCHv2 2.6.24] fib_trie: apply fixes from fib_hash Julian Anastasov
2008-01-29 5:18 ` David Miller [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=20080128.211822.46715588.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=joonwpark81@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robert.olsson@data.slu.se \
/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