From: Jan Kara <jack@suse•cz>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Jan Kara <jack@suse•cz>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Dmitry Monakhov <dmonakhov@openvz•org>
Subject: Re: linux-next: ext3 tree build warning
Date: Tue, 15 Dec 2009 13:24:16 +0100 [thread overview]
Message-ID: <20091215122415.GA5405@quack.suse.cz> (raw)
In-Reply-To: <20091215105925.59a66556.sfr@canb.auug.org.au>
Hi Stephen,
On Tue 15-12-09 10:59:25, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
>
> fs/quota/dquot.c: In function 'dquot_alloc_inode':
> fs/quota/dquot.c:1521: warning: passing argument 1 of 'mark_all_dquot_dirty' discards qualifiers from pointer target type
> fs/quota/dquot.c:327: note: expected 'struct dquot **' but argument is of type 'struct dquot * const*'
> fs/quota/dquot.c: In function 'dquot_free_inode':
> fs/quota/dquot.c:1649: warning: passing argument 1 of 'mark_all_dquot_dirty' discards qualifiers from pointer target type
> fs/quota/dquot.c:327: note: expected 'struct dquot **' but argument is of type 'struct dquot * const*'
>
> Introduced by commit e91077e3d523c2ac2090b3447bf6244567cf7128 ("quota:
> Move duplicated code to separate functions").
Sorry, I forgot to commit this compilation fix before pushing. It should
be fixed now.
Honza
--
Jan Kara <jack@suse•cz>
SUSE Labs, CR
next prev parent reply other threads:[~2009-12-15 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 23:59 linux-next: ext3 tree build warning Stephen Rothwell
2009-12-15 9:58 ` Dmitry Monakhov
2009-12-15 12:35 ` Jan Kara
2009-12-15 12:24 ` Jan Kara [this message]
2009-12-15 12:58 ` Stephen Rothwell
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=20091215122415.GA5405@quack.suse.cz \
--to=jack@suse$(echo .)cz \
--cc=dmonakhov@openvz$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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