linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] remove update_atime
Date: Fri, 4 Nov 2005 17:31:38 -0700	[thread overview]
Message-ID: <20051105003138.GJ31368@schatzie.adilger.int> (raw)
In-Reply-To: <20051104223022.GB9608@lst.de>

On Nov 04, 2005  23:30 +0100, Christoph Hellwig wrote:
> all callers use touch_atime now which takes a vfsmount and allows us
> to implement per-mount noatime.
 
> -EXPORT_SYMBOL(update_atime);
> +EXPORT_SYMBOL(touch_atime);

I would prefer to deprecate update_atime(), instead of removing it
entirely, because it is an exported symbol.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


  reply	other threads:[~2005-11-05  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 22:30 [PATCH 2/2] remove update_atime Christoph Hellwig
2005-11-05  0:31 ` Andreas Dilger [this message]
2005-11-05  0:34   ` Christoph Hellwig

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=20051105003138.GJ31368@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@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 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).