From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: linux-next: build warninga in Linus' tree
Date: Fri, 3 Jun 2011 14:25:34 +0200 [thread overview]
Message-ID: <BANLkTim-0xj7Pr2EkZs2JEkyVw_7F9eM=g@mail.gmail.com> (raw)
In-Reply-To: <20110530113653.5c7084f0.sfr@canb.auug.org.au>
On Mon, May 30, 2011 at 3:36 AM, Stephen Rothwell <sfr@canb.auug.org.au=
> wrote:
> Hi all,
>
> After merging the Linus' tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> fs/btrfs/sysfs.c:76:26: warning: 'btrfs_root_attrs' defined but not u=
sed
> fs/btrfs/sysfs.c:97:26: warning: 'btrfs_super_attrs' defined but not =
used
> fs/btrfs/sysfs.c:153:13: warning: 'btrfs_super_release' defined but n=
ot used
> fs/btrfs/sysfs.c:160:13: warning: 'btrfs_root_release' defined but no=
t used
>
> I have started using gcc v4.5.2 (instead of v4.4.4) if that makes a
> difference.
I see the same warnings with Debian's gcc-4.6 (here: next-20110603),
plus some more:
fs/btrfs/ioctl.c: In function 'btrfs_ioctl_fs_info.isra.24':
fs/btrfs/ioctl.c:2080:1: warning: the frame size of 1032 bytes is
larger than 1024 bytes [-Wframe-larger-than=3D]
fs/btrfs/delayed-inode.c: In function 'btrfs_batch_insert_items':
fs/btrfs/delayed-inode.c:690:9: warning: 'nitems' may be used
uninitialized in this function [-Wuninitialized]
- Sedat -
> --
> Cheers,
> Stephen Rothwell =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
prev parent reply other threads:[~2011-06-03 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 1:36 linux-next: build warninga in Linus' tree Stephen Rothwell
2011-05-31 17:57 ` David Sterba
2011-06-01 15:16 ` Mitch Harder
2011-06-03 11:10 ` David Sterba
2011-06-03 11:38 ` Hugo Mills
2011-06-03 13:16 ` Greg KH
2011-06-03 13:16 ` Greg KH
2011-06-03 12:25 ` Sedat Dilek [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='BANLkTim-0xj7Pr2EkZs2JEkyVw_7F9eM=g@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).