From: "David S. Miller" <davem@redhat.com>
To: chas3@users.sourceforge.net
Cc: chas@cmf.nrl.navy.mil, netdev@oss.sgi.com
Subject: Re: [PATCH][ATM]: better behavior for sendmsg/recvmsg during async closes
Date: Thu, 15 Jan 2004 00:19:21 -0800 [thread overview]
Message-ID: <20040115001921.5d3edcbc.davem@redhat.com> (raw)
In-Reply-To: <200401150416.i0F4GRRr028875@ginger.cmf.nrl.navy.mil>
On Wed, 14 Jan 2004 23:16:28 -0500
chas williams (contractor) <chas@cmf.nrl.navy.mil> wrote:
> 2.6 version of the same 2.4 patch
I applied the 2.6.x version, the 2.4.x version did not apply cleanly at all.
Please regenerate the 2.4.x patch for me, thanks Chas.
next prev parent reply other threads:[~2004-01-15 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 4:16 [PATCH][ATM]: better behavior for sendmsg/recvmsg during async closes chas williams
2004-01-15 8:19 ` David S. Miller [this message]
2004-01-16 3:03 ` chas williams
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 4:16 chas williams
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=20040115001921.5d3edcbc.davem@redhat.com \
--to=davem@redhat.com \
--cc=chas3@users.sourceforge.net \
--cc=chas@cmf.nrl.navy.mil \
--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).