netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy Macleod" <macleodr@nortel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, remi.denis-courmont@nokia.com
Subject: Re: [PATCH 6/6] Phonet: pipe end-point protocol documentation
Date: Tue, 14 Oct 2008 11:06:18 -0400	[thread overview]
Message-ID: <48F4B56A.1070402@nortel.com> (raw)
In-Reply-To: <20081011.123008.251386486.davem@davemloft.net>

David Miller wrote:
> It corrupted the patch, chopping up long lines and such.
> 
> There are directions in linux/Documentation/email-clients.txt on
> how to fix this.
> 
Fixed the line wrapping and RTFM.
Sending a test message to myself worked.

Here's the simple documentation patch, it's against:
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6

// Randy

diff --git a/Documentation/networking/phonet.txt b/Documentation/networking/phonet.txt
index 0e6e592..6a07e45 100644
--- a/Documentation/networking/phonet.txt
+++ b/Documentation/networking/phonet.txt
@@ -146,8 +146,8 @@ WARNING:
 When polling a connected pipe socket for writability, there is an
 intrinsic race condition whereby writability might be lost between the
 polling and the writing system calls. In this case, the socket will
-block until write because possible again, unless non-blocking mode
-becomes enabled.
+block until write becomes possible again, unless non-blocking mode
+is enabled.
 
 
 The pipe protocol provides two socket options at the SOL_PNPIPE level:




  reply	other threads:[~2008-10-14 15:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 10:12 [PATCH 0/6] [RFC] Phonet pipes protocol (v2) Rémi Denis-Courmont
2008-10-01 10:13 ` [PATCH 1/6] Phonet: transport protocol auto-loading Remi Denis-Courmont
2008-10-01 12:45   ` Arnaldo Carvalho de Melo
2008-10-01 15:01     ` Marcel Holtmann
2008-10-03 13:49     ` Rémi Denis-Courmont
2008-10-01 10:13 ` [PATCH 2/6] Phonet: connected sockets glue Remi Denis-Courmont
2008-10-01 12:48   ` Arnaldo Carvalho de Melo
2008-10-01 10:13 ` [PATCH 3/6] Phonet: Pipe End Point for Phonet Pipes protocol Remi Denis-Courmont
2008-10-01 13:18   ` Arnaldo Carvalho de Melo
2008-10-02 10:50     ` Rémi Denis-Courmont
2008-10-02 13:41       ` Arnaldo Carvalho de Melo
2008-10-01 10:13 ` [PATCH 4/6] Phonet: receive pipe control requests as out-of-band data Remi Denis-Courmont
2008-10-01 10:13 ` [PATCH 5/6] Phonet: implement GPRS virtual interface over PEP socket Remi Denis-Courmont
2008-10-01 13:32   ` Arnaldo Carvalho de Melo
2008-10-01 10:13 ` [PATCH 6/6] Phonet: pipe end-point protocol documentation Remi Denis-Courmont
2008-10-01 15:19   ` Randy Macleod
2008-10-10 18:24   ` Randy Macleod
2008-10-11 19:30     ` David Miller
2008-10-14 15:06       ` Randy Macleod [this message]
2008-10-14 20:49         ` David Miller
2008-10-14 15:11       ` Randy Macleod
  -- strict thread matches above, loose matches on Subject: below --
2008-10-03 14:09 [PATCH 0/6] Phonet pipes protocol (take 3) Rémi Denis-Courmont
2008-10-03 14:09 ` [PATCH 6/6] Phonet: pipe end-point protocol documentation Remi Denis-Courmont

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=48F4B56A.1070402@nortel.com \
    --to=macleodr@nortel.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=remi.denis-courmont@nokia.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).