linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Ted Percival <ted@midg3t.net>
Cc: dhowells@redhat.com, linux-arch@vger.kernel.org,
	Ted Percival <ted@tedp.id.au>
Subject: Re: [PATCH 2/2] fcntl.h comment: Fix typo regarding O_SYNC
Date: Fri, 16 Jul 2010 11:00:30 +0100	[thread overview]
Message-ID: <8130.1279274430@redhat.com> (raw)
In-Reply-To: <1279214957-10235-2-git-send-email-ted@tedp.id.au>


Ted Percival <ted@midg3t.net> wrote:

> +/* open/fcntl - O_SYNC is only implemented on block devices and on files
>     located on an ext2 file system */

Is this comment still true about the fact that, with respect to files, this is
only implemented on ext2?

David

  parent reply	other threads:[~2010-07-16 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 17:29 [PATCH 1/2] fcntl.h comment: FD_CLOEXEC is for F_[GET|SET]FD Ted Percival
2010-07-15 17:29 ` [PATCH 2/2] fcntl.h comment: Fix typo regarding O_SYNC Ted Percival
2010-07-16 10:00 ` David Howells [this message]
2010-07-16 11:56   ` Jamie Lokier
2010-07-16 20:51     ` Ted Percival

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=8130.1279274430@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=ted@midg3t.net \
    --cc=ted@tedp.id.au \
    /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).