linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: ericvh@gmail.com
Cc: kernel-mentors@selenic.com, linux-fsdevel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net,
	viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [RFC][2.6 patch 4/7] v9fs 2.0-rc5 - 9P2000 Support For Linux 2.6
Date: Sat, 21 May 2005 01:14:18 +0200	[thread overview]
Message-ID: <20050520231418.GN5112@stusta.de> (raw)
In-Reply-To: <200505182159.j4ILxXH9028708@ms-smtp-01-eri0.texas.rr.com>

On Wed, May 18, 2005 at 04:55:13PM -0500, ericvh@gmail.com wrote:
>...
> --- /dev/null  (tree:6bb5a1cf91bbda8308ec7e6d900cb89071907dcd)
> +++ 3aa81f5c159d11aced6de4ea77d24c36d046bd8e/fs/9p/v9fs_vfs.h  (mode:100644)
>...
> +extern struct super_operations v9fs_super_ops;
>...
> --- /dev/null  (tree:6bb5a1cf91bbda8308ec7e6d900cb89071907dcd)
> +++ 3aa81f5c159d11aced6de4ea77d24c36d046bd8e/fs/9p/vfs_super.c  (mode:100644)
>...
> +static struct super_operations v9fs_super_ops = {
>...

gcc 4.0 correctly complains:

<--  snip  -->

...
  CC [M]  fs/9p/vfs_super.o
fs/9p/vfs_super.c:235: error: static declaration of 'v9fs_super_ops' follows non-static declaration
fs/9p/v9fs_vfs.h:39: error: previous declaration of 'v9fs_super_ops' was here
make[2]: *** [fs/9p/vfs_super.o] Error 1

<--  snip  -->

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2005-05-20 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 21:55 [RFC][2.6 patch 4/7] v9fs 2.0-rc5 - 9P2000 Support For Linux 2.6 ericvh
2005-05-20 23:14 ` Adrian Bunk [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=20050520231418.GN5112@stusta.de \
    --to=bunk@stusta.de \
    --cc=ericvh@gmail.com \
    --cc=kernel-mentors@selenic.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=viro@parcelfarce.linux.theplanet.co.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;
as well as URLs for NNTP newsgroup(s).