From: "David S. Miller" <davem@redhat.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock
Date: Wed, 15 Oct 2003 22:10:20 -0700 [thread overview]
Message-ID: <20031015221020.098f9779.davem@redhat.com> (raw)
In-Reply-To: <20031015113648.GD1174@conectiva.com.br>
On Wed, 15 Oct 2003 08:36:48 -0300
Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
> Em Mon, Oct 13, 2003 at 12:49:30PM -0700, David S. Miller escreveu:
> > Let's do one thing at a time. First, fix the original bug
> > in tcp_ipv4.c by just putting your inet_rcv_saddr() shorthand
> > right there in tcp_ipv4.c and name it tcp4_rcv_saddr() or
> > something like that.
...
> :) Here is the first part:
Perfect, patch applied.
Thanks.
prev parent reply other threads:[~2003-10-16 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 13:13 [PATCH] fixing the cases where tcp_tw_bucket was accessed as a sock Arnaldo Carvalho de Melo
2003-10-13 19:49 ` David S. Miller
2003-10-15 11:36 ` Arnaldo Carvalho de Melo
2003-10-16 5:10 ` David S. Miller [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=20031015221020.098f9779.davem@redhat.com \
--to=davem@redhat.com \
--cc=acme@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 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).