From: Dave Jones <davej@codemonkey.org.uk>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>, Bill Davidsen <davidsen@tmr.com>,
larry@minfin.bg, linux-kernel@vger.kernel.org
Subject: Re: Strange TCP with 2.5.60
Date: Fri, 14 Feb 2003 14:41:51 +0000 [thread overview]
Message-ID: <20030214144151.GA29133@codemonkey.org.uk> (raw)
In-Reply-To: <17320000.1045185481@[10.10.2.4]>
> > Apparently the problem is that this combined with recent seq_file
> > conversions has resulted in changed format of some /proc/net/foo files,
> > which is confusing some network admin apps.
> >
> > It is being worked on.
>
> Can't we do:
>
> - if (iter->zone->fz_next)
> + /* if (iter->zone->fz_next) */
>
> or something similar? Is much less confusing ...
See "It is being worked on" 8-)
Better to fix it properly..
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
prev parent reply other threads:[~2003-02-14 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 11:52 Strange TCP with 2.5.60 Kostadin Karaivanov
2003-02-12 18:24 ` Andrew Morton
2003-02-13 23:27 ` Bill Davidsen
2003-02-13 23:37 ` Andrew Morton
2003-02-14 1:18 ` Martin J. Bligh
2003-02-14 14:41 ` Dave Jones [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=20030214144151.GA29133@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=akpm@digeo.com \
--cc=davidsen@tmr.com \
--cc=larry@minfin.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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