From: Patrick McHardy <kaber@trash.net>
To: "Einar Lück" <lkml@einar-lueck.de>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH 1/2] ipv4 routing: splitting of ip_route_[in|out]put_slow, 2.6.10-rc3
Date: Mon, 20 Dec 2004 15:02:16 +0100 [thread overview]
Message-ID: <41C6DB68.30607@trash.net> (raw)
In-Reply-To: <41C6B3D4.6060207@einar-lueck.de>
Einar Lück wrote:
> [PATCH 1/2] ipv4 routing: splitting of ip_route_[in|out]put_slow,
> 2.6.10-rc3
>
> From: Einar Lueck <lkml@einar-lueck.de>
>
> This patch splits up ip_route_[in|out]put_slow in inlined functions.
> Basic idea:
> * improve overall comprehensibility
> * allow for an easier application of patch for improved multipath
> support (refer to the subsequent patch)
>
> Please consider for application.
Your patches have once again been made unreadable by
your email-client. Please send them again as attachments.
Regards
Patrick
next prev parent reply other threads:[~2004-12-20 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 11:13 [PATCH 1/2] ipv4 routing: splitting of ip_route_[in|out]put_slow, 2.6.10-rc3 Einar Lück
2004-12-20 14:02 ` Patrick McHardy [this message]
2004-12-20 15:08 ` Einar Lück
2005-02-03 1:17 ` David S. Miller
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=41C6DB68.30607@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@einar-lueck.de \
--cc=netdev@oss.sgi.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).