All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: jaredeh@gmail.com
Cc: Linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"Jörn Engel" <joern@logfs.org>,
	tim.bird@am.sony.com, cotte@de.ibm.com, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 04/10] AXFS: axfs_inode.c
Date: Thu, 21 Aug 2008 13:35:35 +0200	[thread overview]
Message-ID: <200808211335.36020.arnd@arndb.de> (raw)
In-Reply-To: <48AD00F0.5030403@gmail.com>

On Thursday 21 August 2008, Jared Hulbert wrote:
> +/***************** functions in other axfs files ******************************/
> +int axfs_get_sb(struct file_system_type *, int, const char *, void *,
> +		struct vfsmount *);
> +void axfs_kill_super(struct super_block *);
> +void axfs_profiling_add(struct axfs_super *, unsigned long, unsigned int);
> +int axfs_copy_mtd(struct super_block *, void *, u64, u64);
> +int axfs_copy_block(struct super_block *, void *, u64, u64);

*Never* put extern declarations into a .c file, that's what headers are for.
If you ever change the definition, the compiler doesn't get a chance to
warn you otherwise.

> +/******************************************************************************/
> +static int axfs_readdir(struct file *, void *, filldir_t);
> +static int axfs_mmap(struct file *, struct vm_area_struct *);
> +static ssize_t axfs_file_read(struct file *, char __user *, size_t, loff_t *);
> +static int axfs_readpage(struct file *, struct page *);
> +static int axfs_fault(struct vm_area_struct *, struct vm_fault *);
> +static struct dentry *axfs_lookup(struct inode *, struct dentry *,
> +				  struct nameidata *);
> +static int axfs_get_xip_mem(struct address_space *, pgoff_t, int, void **,
> +			    unsigned long *);

For style reasons, also please don't put static forward declarations anywhere,
but define the functions in the right order so you don't need them.

	Arnd <><

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: jaredeh@gmail.com
Cc: cotte@de.ibm.com, linux-embedded@vger.kernel.org,
	nickpiggin@yahoo.com.au, "Jörn Engel" <joern@logfs.org>,
	Linux-kernel@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	tim.bird@am.sony.com
Subject: Re: [PATCH 04/10] AXFS: axfs_inode.c
Date: Thu, 21 Aug 2008 13:35:35 +0200	[thread overview]
Message-ID: <200808211335.36020.arnd@arndb.de> (raw)
In-Reply-To: <48AD00F0.5030403@gmail.com>

On Thursday 21 August 2008, Jared Hulbert wrote:
> +/***************** functions in other axfs files ******************************/
> +int axfs_get_sb(struct file_system_type *, int, const char *, void *,
> +		struct vfsmount *);
> +void axfs_kill_super(struct super_block *);
> +void axfs_profiling_add(struct axfs_super *, unsigned long, unsigned int);
> +int axfs_copy_mtd(struct super_block *, void *, u64, u64);
> +int axfs_copy_block(struct super_block *, void *, u64, u64);

*Never* put extern declarations into a .c file, that's what headers are for.
If you ever change the definition, the compiler doesn't get a chance to
warn you otherwise.

> +/******************************************************************************/
> +static int axfs_readdir(struct file *, void *, filldir_t);
> +static int axfs_mmap(struct file *, struct vm_area_struct *);
> +static ssize_t axfs_file_read(struct file *, char __user *, size_t, loff_t *);
> +static int axfs_readpage(struct file *, struct page *);
> +static int axfs_fault(struct vm_area_struct *, struct vm_fault *);
> +static struct dentry *axfs_lookup(struct inode *, struct dentry *,
> +				  struct nameidata *);
> +static int axfs_get_xip_mem(struct address_space *, pgoff_t, int, void **,
> +			    unsigned long *);

For style reasons, also please don't put static forward declarations anywhere,
but define the functions in the right order so you don't need them.

	Arnd <><

  parent reply	other threads:[~2008-08-21 11:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  5:45 [PATCH 04/10] AXFS: axfs_inode.c Jared Hulbert
2008-08-21  5:45 ` Jared Hulbert
2008-08-21  8:35 ` Carsten Otte
2008-08-21  8:35   ` Carsten Otte
2008-08-21 11:35 ` Arnd Bergmann [this message]
2008-08-21 11:35   ` Arnd Bergmann
2008-08-21 12:17 ` Arnd Bergmann
2008-08-21 12:17   ` Arnd Bergmann
2008-08-21 12:17   ` Arnd Bergmann
2008-08-21 15:06   ` Jared Hulbert
2008-08-21 15:06     ` Jared Hulbert
2008-08-21 15:12     ` Arnd Bergmann
2008-08-21 15:12       ` Arnd Bergmann
2008-08-21 15:12       ` Arnd Bergmann
2008-08-22  2:22   ` Phillip Lougher
2008-08-22  2:22     ` Phillip Lougher
2008-08-22  3:23     ` Jared Hulbert
2008-08-22  3:23       ` Jared Hulbert
2008-08-22  3:29       ` Phillip Lougher
2008-08-22  3:29         ` Phillip Lougher
2008-08-22 10:00     ` Arnd Bergmann
2008-08-22 10:00       ` Arnd Bergmann
2008-08-22 17:08       ` Phillip Lougher
2008-08-22 17:08         ` Phillip Lougher
2008-08-22 17:19         ` Jörn Engel
2008-08-22 17:19           ` Jörn Engel
2008-08-22 17:19           ` Jörn Engel
2008-08-22 18:04           ` Jared Hulbert
2008-08-22 18:04             ` Jared Hulbert
2008-08-22  0:21 ` Phillip Lougher
2008-08-22  0:21   ` Phillip Lougher
2008-08-22  0:21   ` Phillip Lougher
2008-08-22  3:27   ` Jared Hulbert
2008-08-22  3:27     ` Jared Hulbert
2008-08-22  3:46     ` Phillip Lougher
2008-08-22  3:46       ` Phillip Lougher

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=200808211335.36020.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=cotte@de.ibm.com \
    --cc=jaredeh@gmail.com \
    --cc=joern@logfs.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tim.bird@am.sony.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.