From: "David S. Miller" <davem@redhat.com>
To: chas3@users.sourceforge.net, chas@cmf.nrl.navy.mil
Cc: netdev@oss.sgi.com
Subject: Re: [rfc] sk_write_space() for atm
Date: Tue, 24 Jun 2003 17:40:42 -0700 (PDT) [thread overview]
Message-ID: <20030624.174042.27809957.davem@redhat.com> (raw)
In-Reply-To: <200306250032.h5P0WJsG010081@ginger.cmf.nrl.navy.mil>
From: chas williams <chas@cmf.nrl.navy.mil>
Date: Tue, 24 Jun 2003 20:30:12 -0400
comments?
This looks ok to me, but I am not well versed in this
area. For example, if you give a spurious wakeup via
poll() what can happen?
next prev parent reply other threads:[~2003-06-25 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 17:33 [rfc] sk_write_space() for atm chas williams
2003-06-24 23:35 ` David S. Miller
2003-06-25 0:30 ` chas williams
2003-06-25 0:40 ` David S. Miller [this message]
2003-06-25 2:31 ` 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=20030624.174042.27809957.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).