mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linuxram@us.ibm.com (Ram)
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linuxram@us.ibm.com, viro@ftp.linux.org.uk, miklos@szeredi.hu,
	mike@waychison.com, bfields@fieldses.org, serue@us.ibm.com
Subject: Re: [RFC PATCH 1/10] vfs: Lindentified namespace.c
Date: Fri, 16 Sep 2005 14:25:57 -0700	[thread overview]
Message-ID: <20050916142557.691b055e.akpm@osdl.org> (raw)
In-Reply-To: <20050916182619.GA28428@RAM>

linuxram@us.ibm.com (Ram) wrote:
>
> Lindentified fs/namespace.c

For something which is as already-close to CodingStyle as namespace.c it's
probably better to tidy it up by hand.  Lindent breaks almost as much stuff
as it fixes.

> -static void *m_start(struct seq_file *m, loff_t *pos)
> +static void *m_start(struct seq_file *m, loff_t * pos)

As Ben said.

>  	list_for_each(p, &n->list)
> -		if (!l--)
> -			return list_entry(p, struct vfsmount, mnt_list);
> +	    if (!l--)
> +		return list_entry(p, struct vfsmount, mnt_list);

Indenting with four spaces is a bit of a pain.  Presumably because Lindent
doesn't know what list_for_each() does.

> -static void *m_next(struct seq_file *m, void *v, loff_t *pos)
> +static void *m_next(struct seq_file *m, void *v, loff_t * pos)

Again.

>  struct seq_operations mounts_op = {
> -	.start	= m_start,
> -	.next	= m_next,
> -	.stop	= m_stop,
> -	.show	= show_vfsmnt
> +	.start = m_start,
> +	.next = m_next,
> +	.stop = m_stop,
> +	.show = show_vfsmnt
>  };

Arguable.

> -repeat:
> +      repeat:

Labels go in column zero.

> -dput_and_out:
> +      dput_and_out:

ugh, here it went and inserted spaces.

> -	while(d_mountpoint(nd->dentry) && follow_down(&nd->mnt, &nd->dentry))
> -		;
> +	while (d_mountpoint(nd->dentry) && follow_down(&nd->mnt, &nd->dentry)) ;

Regression!

> -	error = __user_walk(new_root, LOOKUP_FOLLOW|LOOKUP_DIRECTORY, &new_nd);
> +	error =
> +	    __user_walk(new_root, LOOKUP_FOLLOW | LOOKUP_DIRECTORY, &new_nd);

ug.

> ...

etc.

One approach is to run Lindent, then go through the diff and fix it up by
hand.  Then apply the patch and fix up the remaining Lindent mistakes by
hand.  But the raw output of Lindent isn't right.

  parent reply	other threads:[~2005-09-16 21:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 18:26 Ram
2005-09-16 18:51 ` Alexey Dobriyan
2005-09-16 20:55 ` Benjamin LaHaise
2005-09-16 21:29   ` Ram Pai
2005-09-16 21:25 ` Andrew Morton [this message]
2005-09-16 21:38   ` Matthew Wilcox
2005-09-16 21:39   ` Ram Pai
2005-09-17 12:18     ` Jörn Engel
2005-09-17 12:34       ` Al Viro
2005-09-17 13:33         ` Jörn Engel

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=20050916142557.691b055e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bfields@fieldses.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=mike@waychison.com \
    --cc=miklos@szeredi.hu \
    --cc=serue@us.ibm.com \
    --cc=viro@ftp.linux.org.uk \
    /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

all inboxes | Powered by JetHome®