cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 1/2] gfs2: use list_for_each_entry instead
Date: Tue, 14 Aug 2007 11:18:43 +0100	[thread overview]
Message-ID: <1187086723.8765.840.camel@quoit> (raw)
In-Reply-To: <11867992283116-git-send-email-crquan@gmail.com>

Hi,

Both of these patches are now in the -nmw git tree. Thanks,

Steve.

On Sat, 2007-08-11 at 10:27 +0800, Denis Cheng wrote:
> Signed-off-by: Denis Cheng <crquan@gmail.com>
> ---
>  fs/gfs2/ops_fstype.c |    4 +---
>  1 files changed, 1 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
> index cf5aa50..8d3389f 100644
> --- a/fs/gfs2/ops_fstype.c
> +++ b/fs/gfs2/ops_fstype.c
> @@ -818,7 +818,6 @@ static struct super_block* get_gfs2_sb(const char *dev_name)
>  	struct nameidata nd;
>  	struct file_system_type *fstype;
>  	struct super_block *sb = NULL, *s;
> -	struct list_head *l;
>  	int error;
>  
>  	error = path_lookup(dev_name, LOOKUP_FOLLOW, &nd);
> @@ -830,8 +829,7 @@ static struct super_block* get_gfs2_sb(const char *dev_name)
>  	error = vfs_getattr(nd.mnt, nd.dentry, &stat);
>  
>  	fstype = get_fs_type("gfs2");
> -	list_for_each(l, &fstype->fs_supers) {
> -		s = list_entry(l, struct super_block, s_instances);
> +	list_for_each_entry(s, &fstype->fs_supers, s_instances) {
>  		if ((S_ISBLK(stat.mode) && s->s_dev == stat.rdev) ||
>  		    (S_ISDIR(stat.mode) && s == nd.dentry->d_inode->i_sb)) {
>  			sb = s;



           reply	other threads:[~2007-08-14 10:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <11867992283116-git-send-email-crquan@gmail.com>]

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=1187086723.8765.840.camel@quoit \
    --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 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).