From: David Miller <davem@davemloft.net>
To: vnuorval@tcs.hut.fi
Cc: yoshfuji@linux-ipv6.org, tgraf@suug.ch, kim.nordlund@nokia.com,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/13] [IPV6] Clean up BACKTRACK().
Date: Mon, 16 Oct 2006 22:11:46 -0700 (PDT) [thread overview]
Message-ID: <20061016.221146.66060975.davem@davemloft.net> (raw)
In-Reply-To: <45341E83.7010409@tcs.hut.fi>
From: Ville Nuorvala <vnuorval@tcs.hut.fi>
Date: Tue, 17 Oct 2006 03:06:27 +0300
> The fn check is unnecessary as fn can never be NULL in BACKTRACK().
>
> Signed-off-by: Ville Nuorvala <vnuorval@tcs.hut.fi>
Applied, especially valid since we're walking parents up to
the, we break out at hitting root, and root's parent is
itself :-)
Thanks.
prev parent reply other threads:[~2006-10-17 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 0:06 [PATCH 4/13] [IPV6] Clean up BACKTRACK() Ville Nuorvala
2006-10-17 5:11 ` 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=20061016.221146.66060975.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kim.nordlund@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=vnuorval@tcs.hut.fi \
--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).