From: Phillip Lougher <phillip@lougher•demon.co.uk>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Stephen Hemminger <shemminger@vyatta•com>
Subject: Re: linux-next: build warning after merge of the squashfs tree
Date: Sun, 23 May 2010 03:39:54 +0100 [thread overview]
Message-ID: <4BF8957A.9090506@lougher.demon.co.uk> (raw)
In-Reply-To: <20100522163042.13478ac4.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Phillip,
>
> After merging the squashfs tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> fs/squashfs/super.c: In function 'squashfs_fill_super':
> fs/squashfs/super.c:265: warning: assignment from incompatible pointer type
>
> Introduced by commit 67f66cc6c728de183d9d43c243cb163c1ebd8e04 ("squashfs:
> add new extended inode types") from the squashfs tree interacting with
> commit bb4354538eb7b92f32cfedbad68c7be266c0b467 ("fs: xattr_handler table
> should be const") from Linus' tree.
Fixed. Thanks.
Phillip
prev parent reply other threads:[~2010-05-23 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 6:30 linux-next: build warning after merge of the squashfs tree Stephen Rothwell
2010-05-23 2:39 ` Phillip Lougher [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=4BF8957A.9090506@lougher.demon.co.uk \
--to=phillip@lougher$(echo .)demon.co.uk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shemminger@vyatta$(echo .)com \
/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