On Wed 06-02-08 17:35:39, Andreas Schwab wrote:
> Jan Kara <[EMAIL PROTECTED]> writes:
>
> > Add explanation of I_DIRTY_DATASYNC bit.
> >
> > Signed-off-by: Jan Kara <[EMAIL PROTECTED]>
> >
> > 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.
Oh, OK. Thanks for spotting this. Just next to tab ;). I'll resend a
patch without the typo.
Honza
--
Jan Kara <[EMAIL PROTECTED]>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
