From: Olaf Hering <olh@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: marcelo@conectiva.com.br, netdev@oss.sgi.com
Subject: Re: comment about struct tcp_tw_bucket in struct sock
Date: Wed, 14 May 2003 10:00:43 +0200 [thread overview]
Message-ID: <20030514080043.GA2575@suse.de> (raw)
In-Reply-To: <20030513.163150.28800008.davem@redhat.com>
On Tue, May 13, David S. Miller wrote:
> From: Olaf Hering <olh@suse.de>
> Date: Tue, 13 May 2003 23:05:41 +0200
>
> we just hit this one. struct tcp_tw_bucket and stuct sock must match.
>
> Please apply.
>
> It's documented in tcp.h already.
True, but not in struct sock.
--
USB is for mice, FireWire is for men!
next prev parent reply other threads:[~2003-05-14 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 21:05 comment about struct tcp_tw_bucket in struct sock Olaf Hering
2003-05-13 23:31 ` David S. Miller
2003-05-14 2:44 ` Arnaldo Carvalho de Melo
2003-05-14 8:00 ` Olaf Hering [this message]
2003-05-14 19:17 ` David S. Miller
2003-05-14 19:23 ` Andi Kleen
2003-05-14 19:34 ` David S. Miller
2003-05-14 19:57 ` Andi Kleen
2003-05-14 20:02 ` David S. Miller
2003-05-14 8:32 ` Andi Kleen
2003-05-14 19:18 ` David S. Miller
2003-05-14 19:21 ` Andi Kleen
2003-05-22 0:52 ` Arnaldo Carvalho de Melo
2003-05-22 8:02 ` Andi Kleen
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=20030514080043.GA2575@suse.de \
--to=olh@suse.de \
--cc=davem@redhat.com \
--cc=marcelo@conectiva.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.