From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Mingming Cao <cmm@us.ibm.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: linux-next: quota tree build warning
Date: Thu, 5 Feb 2009 12:53:19 +0100 [thread overview]
Message-ID: <20090205115318.GA22417@duck.suse.cz> (raw)
In-Reply-To: <20090205172823.e6b203bf.sfr@canb.auug.org.au>
Hi Stephen,
On Thu 05-02-09 17:28:23, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
>
> fs/ext4/super.c:949: warning: initialization from incompatible pointer type
>
> The line is this:
>
> .get_reserved_space = ext4_get_reserved_space,
>
> Where ext4_get_reserved_space() returns unsigned long long, but the
> get_reserved_space prototype returns a qsize_t (which is long long).
>
> Introduced by commit dafa34c7ba30012a7cacffb98e978e5edb74457f ("ext4: quota
> reservation for delayed allocation").
Thanks. Should be fixed now.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2009-02-05 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 6:28 linux-next: quota tree build warning Stephen Rothwell
2009-02-05 11:53 ` Jan Kara [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=20090205115318.GA22417@duck.suse.cz \
--to=jack@suse.cz \
--cc=cmm@us.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/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