netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: acme@conectiva.com.br, netdev@oss.sgi.com
Subject: Re: [TCP] Fixed bug that hid sockets in tcp_diag
Date: Tue, 5 Oct 2004 22:22:02 -0700	[thread overview]
Message-ID: <20041005222202.0d1d9be0.davem@davemloft.net> (raw)
In-Reply-To: <20041006035801.GA15940@gondor.apana.org.au>

On Wed, 6 Oct 2004 13:58:01 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> This patch squashes a bug in tcp_diag which was created when the
> sk_* loops replaced the original for loops.  It's a pity that these
> sk_*/hlist_*/list_* loops don't take an arbitrary expression as an
> argument for continue.
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Thanks a lot for fixing this bug Herbert, patch applied.

Did you send this patch to the original bug reporter for
testing?  What was the result?

  reply	other threads:[~2004-10-06  5:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06  3:58 [TCP] Fixed bug that hid sockets in tcp_diag Herbert Xu
2004-10-06  5:22 ` David S. Miller [this message]
2004-10-06  6:02   ` Herbert Xu

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=20041005222202.0d1d9be0.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=acme@conectiva.com.br \
    --cc=herbert@gondor.apana.org.au \
    --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).