From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] common code for generating tcp_info
Date: Fri, 4 Jun 2004 20:57:49 -0700 [thread overview]
Message-ID: <20040604205749.11725598.davem@redhat.com> (raw)
In-Reply-To: <20040604153749.5d8a13b9@dell_ss3.pdx.osdl.net>
On Fri, 4 Jun 2004 15:37:49 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> There are two places tcp_diag (netlink) and getsockopt, both with almost
> the same code to generate tcp_info from the current socket state.
Works for me, applied.
Should maybe try to move that tcp_info off the stack at some
point.
next prev parent reply other threads:[~2004-06-05 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 22:37 [PATCH] common code for generating tcp_info Stephen Hemminger
2004-06-05 3:57 ` David S. Miller [this message]
2004-06-07 17:07 ` [PATCH] add receive DRS info Stephen Hemminger
2004-06-07 22:27 ` David S. Miller
2004-06-07 14:48 ` [PATCH] common code for generating tcp_info Joe Perches
2004-06-07 16:16 ` Stephen Hemminger
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=20040604205749.11725598.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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).