From: "David S. Miller" <davem@davemloft.net>
To: akpm@osdl.org
Cc: jgarzik@pobox.com, netdev@oss.sgi.com, akpm@osdl.org,
ahendry@tusc.com.au
Subject: Re: [patch 6/9] X.25: Stop /proc/net/x25/route infinitely reading
Date: Thu, 28 Oct 2004 16:47:49 -0700 [thread overview]
Message-ID: <20041028164749.58cde95e.davem@davemloft.net> (raw)
In-Reply-To: <200410280721.i9S7Li908005@mail.osdl.org>
On Thu, 28 Oct 2004 00:19:45 -0700
akpm@osdl.org wrote:
> From: Andrew Hendry <ahendry@tusc.com.au>
>
> route add --x25 0/0 eth0
> cat /proc/net/x25/route
> reads the single routing entry forever.
>
> This patch makes x25_get_route_idx behave the same as x25_get_socket_idx
> which works correctly.
>
> Signed-off-by: Andrew Hendry <ahendry@tusc.com.au>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
Applied, thanks.
prev parent reply other threads:[~2004-10-28 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 7:19 [patch 6/9] X.25: Stop /proc/net/x25/route infinitely reading akpm
2004-10-28 23:47 ` David S. 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=20041028164749.58cde95e.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ahendry@tusc.com.au \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--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).