From: David Miller <davem@davemloft.net>
To: ramirose@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6.25] [IPV4] Remove unused multipath cached routing defintion in net/flow.h
Date: Mon, 31 Dec 2007 04:29:22 -0800 (PST) [thread overview]
Message-ID: <20071231.042922.37372731.davem@davemloft.net> (raw)
In-Reply-To: <eb3ff54b0712310315l4df16c6fye0bf2a82505d20be@mail.gmail.com>
From: "Rami Rosen" <ramirose@gmail.com>
Date: Mon, 31 Dec 2007 13:15:19 +0200
> The FLOWI_FLAG_MULTIPATHOLDROUTE definition in include/net/flow.h is an unused
> definition. It belongs to IPV4 multipath cached routing support,
> which has been dropped recently for 2.6.23 kernel (July 2007).
Yep.
> http://www.linux-foundation.org/en/Net:Network_Overview
Why do you keep listing this URL? Is this your signature? :-/
I don't think the 1000 or so folks on this list need to see
that same URL every time you post a patch, thanks.
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Patch applied, thank you.
prev parent reply other threads:[~2007-12-31 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 11:15 [PATCH net-2.6.25] [IPV4] Remove unused multipath cached routing defintion in net/flow.h Rami Rosen
2007-12-31 12:29 ` 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=20071231.042922.37372731.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ramirose@gmail.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