[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120713144244.f3c9fb27.akpm@linux-foundation.org>
Date: Fri, 13 Jul 2012 14:42:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: dedekind1@...il.com
Cc: Al Viro <viro@...IV.linux.org.uk>,
Linux Kernel Maling List <linux-kernel@...r.kernel.org>,
Linux FS Maling List <linux-fsdevel@...r.kernel.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 0/3] fs/sysv: stop using write_supers and s_dirt
On Thu, 12 Jul 2012 17:37:58 +0300
Artem Bityutskiy <dedekind1@...il.com> wrote:
> On Tue, 2012-07-03 at 16:43 +0300, Artem Bityutskiy wrote:
> > This patch-set makes sysv file-system stop using the VFS '->write_supers()'
> > call-back and the '->s_dirt' superblock field because I plan to remove them
> > once all users are gone.
>
> Hi Andrew,
>
> would you please pick this patch-set as well? I also sent you an update
> for hfs and hfsplus file-systems today - found a bug while doing some
> more testing. Also, I sent UFS changes today, very similar. Most
> probably no one will reply and I hope you would pick them as well.
>
The issue Alan raised around the superblock timestamp is still up in
the air. I guess he's a slow typist ;)
My take is "no, we don't need to do that any more" - surely all Linux
systems have a functional hardware clock. But the changelog should be
updated to describe and justify the decision.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists