All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 1/5] GFS2: Rename function gfs2_close to gfs2_release
Date: Thu, 12 Apr 2012 11:44:09 +0100	[thread overview]
Message-ID: <1334227449.2697.2.camel@menhir> (raw)
In-Reply-To: <80cd3e23-ca11-41e1-afd2-dca372c39a08@zmail12.collab.prod.int.phx2.redhat.com>

Hi,

All five patches are in the -nmw tree now. Thanks,

Steve.

On Wed, 2012-04-11 at 12:56 -0400, Bob Peterson wrote:
> Hi,
> 
> This patch renames function gfs2_close to gfs2_release.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 
> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> ---
> From: Bob Peterson <rpeterso@redhat.com>
> Date: Mon, 12 Mar 2012 10:56:01 -0500
> Subject: [PATCH 1/5] GFS2: Rename function gfs2_close to gfs2_release
> 
> VFS now calls a release function where it used to call a close
> function. This patch renames gfs2_close to gfs2_release so that
> it makes more sense to someone reading the code.
> ---
>  fs/gfs2/file.c |   12 ++++++------
>  1 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
> index 7683458..916490f 100644
> --- a/fs/gfs2/file.c
> +++ b/fs/gfs2/file.c
> @@ -559,14 +559,14 @@ fail:
>  }
>  
>  /**
> - * gfs2_close - called to close a struct file
> + * gfs2_release - called to close a struct file
>   * @inode: the inode the struct file belongs to
>   * @file: the struct file being closed
>   *
>   * Returns: errno
>   */
>  
> -static int gfs2_close(struct inode *inode, struct file *file)
> +static int gfs2_release(struct inode *inode, struct file *file)
>  {
>  	struct gfs2_sbd *sdp = inode->i_sb->s_fs_info;
>  	struct gfs2_file *fp;
> @@ -1006,7 +1006,7 @@ const struct file_operations gfs2_file_fops = {
>  	.unlocked_ioctl	= gfs2_ioctl,
>  	.mmap		= gfs2_mmap,
>  	.open		= gfs2_open,
> -	.release	= gfs2_close,
> +	.release	= gfs2_release,
>  	.fsync		= gfs2_fsync,
>  	.lock		= gfs2_lock,
>  	.flock		= gfs2_flock,
> @@ -1020,7 +1020,7 @@ const struct file_operations gfs2_dir_fops = {
>  	.readdir	= gfs2_readdir,
>  	.unlocked_ioctl	= gfs2_ioctl,
>  	.open		= gfs2_open,
> -	.release	= gfs2_close,
> +	.release	= gfs2_release,
>  	.fsync		= gfs2_fsync,
>  	.lock		= gfs2_lock,
>  	.flock		= gfs2_flock,
> @@ -1038,7 +1038,7 @@ const struct file_operations gfs2_file_fops_nolock = {
>  	.unlocked_ioctl	= gfs2_ioctl,
>  	.mmap		= gfs2_mmap,
>  	.open		= gfs2_open,
> -	.release	= gfs2_close,
> +	.release	= gfs2_release,
>  	.fsync		= gfs2_fsync,
>  	.splice_read	= generic_file_splice_read,
>  	.splice_write	= generic_file_splice_write,
> @@ -1050,7 +1050,7 @@ const struct file_operations gfs2_dir_fops_nolock = {
>  	.readdir	= gfs2_readdir,
>  	.unlocked_ioctl	= gfs2_ioctl,
>  	.open		= gfs2_open,
> -	.release	= gfs2_close,
> +	.release	= gfs2_release,
>  	.fsync		= gfs2_fsync,
>  	.llseek		= default_llseek,
>  };




      reply	other threads:[~2012-04-12 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0630d251-a5cc-446a-bc7a-1e87e75ab0e8@zmail12.collab.prod.int.phx2.redhat.com>
2012-04-11 16:56 ` [Cluster-devel] [GFS2 PATCH 1/5] GFS2: Rename function gfs2_close to gfs2_release Bob Peterson
2012-04-12 10:44   ` Steven Whitehouse [this message]

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=1334227449.2697.2.camel@menhir \
    --to=swhiteho@redhat.com \
    /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.