All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add explanation of I_DIRTY_DATASYNC bit
Date: Wed, 06 Feb 2008 17:35:39 +0100	[thread overview]
Message-ID: <jeejbqt544.fsf@sykes.suse.de> (raw)
In-Reply-To: <20080206162920.GB3475@duck.suse.cz> (Jan Kara's message of "Wed\, 6 Feb 2008 17\:29\:20 +0100")

Jan Kara <jack@suse.cz> writes:

> Add explanation of I_DIRTY_DATASYNC bit.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 56bd421..475125e 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -1280,7 +1280,10 @@ struct super_operations {
>   * Two bits are used for locking and completion notification, I_LOCK and I_SYNC.
>   *
>   * I_DIRTY_SYNC		Inode itself is dirty.
> - * I_DIRTY_DATASYNC	Data-related inode changes pending
> + * I_DIRTY_DATASYNC	Data-related inode changes pending. We keep track of
> + *		`	these changes separately from I_DIRTY_SYNC so that we
                ^

Looks like a typo.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2008-02-06 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 16:29 [PATCH] Add explanation of I_DIRTY_DATASYNC bit Jan Kara
2008-02-06 16:35 ` Andreas Schwab [this message]
2008-02-06 16:54   ` Jan Kara
2008-02-06 16:56 ` Jan Kara

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=jeejbqt544.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.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 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.