All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	"YOSHIFUJI Hideaki / _$B5HF#1QL@" <yoshfuji@linux-ipv6.org>,
	netdev@oss.sgi.com
Subject: Re: [PATCH] Tcp port selection for IPV6.
Date: Thu, 20 Jan 2005 22:53:18 -0200	[thread overview]
Message-ID: <39e6f6c705012016537fa48ca4@mail.gmail.com> (raw)
In-Reply-To: <20050120164529.6d6a5f0b@dxpl.pdx.osdl.net>

On Thu, 20 Jan 2005 16:45:29 -0800, Stephen Hemminger
<shemminger@osdl.org> wrote:

> Now the code in ipv4/tcp_ipv4.c and ipv6/tcp_ipv6.c are
> almost identical for tcp_hash_connect.

Humm,  dccp_hash_connect is almost identical to tcp_hash_connect too...  /me
adds an entry to his TODO list... :-)

- Arnaldo

  reply	other threads:[~2005-01-21  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21  0:45 [PATCH] Tcp port selection for IPV6 Stephen Hemminger
2005-01-21  0:53 ` Arnaldo Carvalho de Melo [this message]
2005-01-26  6:25 ` David S. Miller
2005-02-09  4:38 ` David S. Miller

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=39e6f6c705012016537fa48ca4@mail.gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.org \
    --cc=yoshfuji@linux-ipv6.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 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.