From: Patrick McHardy <kaber@trash.net>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] IPROUTE2: Fix bug in display of ipv6 cloned/cached routes
Date: Fri, 13 Jul 2007 14:53:49 +0200 [thread overview]
Message-ID: <469775DD.3090302@trash.net> (raw)
In-Reply-To: <1184268044.12609.21.camel@localhost.localdomain>
Sridhar Samudrala wrote:
> I found an issue with my original patch. If cache/cloned is
> specified, it dumps the cloned routes irrespective of the table
> specified. I think this is a better fix and also should address
> the case you were mentioning above.
Your patch looks good, thanks.
prev parent reply other threads:[~2007-07-13 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 18:37 [PATCH] IPROUTE2: Fix bug in display of ipv6 cloned/cached routes Sridhar Samudrala
2007-07-11 18:46 ` Patrick McHardy
2007-07-12 19:20 ` Sridhar Samudrala
2007-07-13 12:53 ` Patrick McHardy [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=469775DD.3090302@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=sri@us.ibm.com \
/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).