All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>
Cc: "Stuart MacDonald" <stuartm@connecttech.com>,
	linux-kernel@vger.kernel.org
Subject: Re: TCP stack behaviour question
Date: Tue, 19 Sep 2006 08:47:10 +0200	[thread overview]
Message-ID: <200609190847.10882.ak@suse.de> (raw)
In-Reply-To: <20060919061335.113810@gmx.net>

On Tuesday 19 September 2006 08:13, Michael Kerrisk wrote:
> Von: "Stuart MacDonald" <stuartm@connecttech.com>
> 
> > > > Ok maybe it's a bit misleading. Michael, you might want to clarify.
> > > 
> > > Can some one of you propose a better text please?
> > 
> > Perhaps
> > 
> > Note that TCP has no error queue; MSG_ERRQUEUE is illegal on
> > SOCK_STREAM sockets.  IP_RECVERR is valid for TCP, but all errors are
> > returned by socket function return or SO_ERROR only.
> > 
> > ?
> 
> Sound okay to you Andi?

Yes.
-Andi

  reply	other threads:[~2006-09-19  6:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 17:28 TCP stack behaviour question Stuart MacDonald
2006-09-18  8:29 ` Andi Kleen
2006-09-18 13:20   ` Stuart MacDonald
2006-09-18 13:54     ` Andi Kleen
2006-09-18 14:19       ` Stuart MacDonald
2006-09-18 14:31         ` Andi Kleen
2006-09-18 15:38           ` Michael Kerrisk
2006-09-18 17:01             ` Stuart MacDonald
2006-09-19  6:13               ` Michael Kerrisk
2006-09-19  6:47                 ` Andi Kleen [this message]
2006-09-19 14:50               ` Michael Kerrisk
2006-09-20  9:55                 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-09-18 18:29 Stuart MacDonald
2006-09-19 12:03 ` Samuel Tardieu
2006-09-19 14:00   ` Stuart MacDonald
2006-09-20  9:54     ` Andi Kleen

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=200609190847.10882.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-manpages@gmx.net \
    --cc=stuartm@connecttech.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 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.