From: Jens Axboe <jens.axboe@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: block tree build warning
Date: Fri, 4 Sep 2009 09:57:27 +0200 [thread overview]
Message-ID: <20090904075726.GS18599@kernel.dk> (raw)
In-Reply-To: <20090904175440.09a67ee7.sfr@canb.auug.org.au>
On Fri, Sep 04 2009, Stephen Rothwell wrote:
> Hi Jens,
>
> Today's linux-next build (powerpc allnoconfig) produced this warning:
>
> fs/fs-writeback.c: In function 'sync_inodes_sb':
> fs/fs-writeback.c:1140: warning: overflow in implicit constant conversion
>
> Introduced by commit bda31e6ac21d7d41525c4e57549ac24bacdcf622
> ("writeback: get rid of generic_sync_sb_inodes() export"). This is a
> 32bit build.
This is now fixed, I'll push out a new for-next in 2 seconds... And
done, should be OK now.
--
Jens Axboe
next prev parent reply other threads:[~2009-09-04 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 7:54 linux-next: block tree build warning Stephen Rothwell
2009-09-04 7:57 ` Jens Axboe [this message]
2009-09-04 8:27 ` 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=20090904075726.GS18599@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).