LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Erez Zadok <ezk@cs.sunysb.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, ezk@cs.sunysb.edu, rdunlap@xenotime.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix up kerneldoc in fs/ioctl.c a little bit
Date: Sat, 9 Feb 2008 02:19:27 -0500	[thread overview]
Message-ID: <200802090719.m197JRan023715@agora.fsl.cs.sunysb.edu> (raw)
In-Reply-To: Your message of "Sat, 09 Feb 2008 08:15:59 +0100." <20080209071559.GA30903@lst.de>

In message <20080209071559.GA30903@lst.de>, Christoph Hellwig writes:
>  - remove non-standard in/out markers
>  - use tabs for formatting
> 
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Index: linux-2.6/fs/ioctl.c
> ===================================================================
> --- linux-2.6.orig/fs/ioctl.c	2008-02-09 07:49:02.000000000 +0100
> +++ linux-2.6/fs/ioctl.c	2008-02-09 07:49:20.000000000 +0100
> @@ -18,9 +18,9 @@
>  
>  /**
>   * vfs_ioctl - call filesystem specific ioctl methods
> - * @filp: [in]     open file to invoke ioctl method on
> - * @cmd:  [in]     ioctl command to execute
> - * @arg:  [in/out] command-specific argument for ioctl
> + * @filp:	open file to invoke ioctl method on
> + * @cmd:	ioctl command to execute
> + * @arg:	command-specific argument for ioctl
>   *
>   * Invokes filesystem specific ->unlocked_ioctl, if one exists; otherwise
>   * invokes * filesystem specific ->ioctl method.  If neither method exists,
              ^

I also think this extra '*' in the last comment line above is spurious,
perhaps the result of a paragraph reformatting command that mixed comment
*'s with text.

Erez.

  reply	other threads:[~2008-02-09  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09  7:15 Christoph Hellwig
2008-02-09  7:19 ` Erez Zadok [this message]
2008-02-09  7:22   ` 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=200802090719.m197JRan023715@agora.fsl.cs.sunysb.edu \
    --to=ezk@cs.sunysb.edu \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --subject='Re: [PATCH] fix up kerneldoc in fs/ioctl.c a little bit' \
    /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

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).