mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Fredrik Noring <noring@nocrew.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Improving read/write/close system call reliability when used with pthreads
Date: Sun, 12 Aug 2007 07:17:21 -0700	[thread overview]
Message-ID: <20070812071721.f35d7373.pj@sgi.com> (raw)
In-Reply-To: <70E19A0A-2728-4ADA-B984-A36182C1F575@nocrew.org>

Fredrik wrote:
> required-fds.patch (not sure Apple Mail can handle this properly  
> though...):

You suspected correctly - Apple Mail line wrapped it at 72 columns
(added newlines in any line going past column 72.)  This makes it
impossible to apply the patch without alot of hand editing.

As you probably also suspect (correctly, again), given the volume of
patches we handle on lkml, the burden is on the submitter to get the
patch format correct, so it applies cleanly.

You will have to experiment some, sending the patch to yourself and
being sure that it applies cleanly.  I'm not an Apple Mail expert, so
can't help; sorry.  Perhaps some other email program ...?


For example, this line wrapped:

fs/open.c                 |   63 +++++++++++++++++++++++++++++++++++++ 
+++++++++

and more critically, in the patch, many lines, such as:

+/* file descriptors required to complete current I/O operation  
successfully */
+	struct list_head required_fds;



-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2007-08-12 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 13:03 Fredrik Noring
2007-08-12 14:17 ` Paul Jackson [this message]
2007-08-12 18:30   ` [PATCH] " Fredrik Noring
2007-08-12 15:13 ` Alan Cox
2007-08-12 16:33   ` Fredrik Noring
2007-08-12 18:55     ` Alan Cox
2007-08-12 19:19       ` Fredrik Noring
2007-08-13  3:14     ` David Schwartz
2007-08-13  6:50       ` Fredrik Noring

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=20070812071721.f35d7373.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noring@nocrew.org \
    /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

all inboxes | Powered by JetHome®