public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jens Axboe <jens.axboe@oracle•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: block tree build warning
Date: Fri, 4 Sep 2009 17:54:40 +1000	[thread overview]
Message-ID: <20090904175440.09a67ee7.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

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.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-09-04  7:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04  7:54 Stephen Rothwell [this message]
2009-09-04  7:57 ` linux-next: block tree build warning Jens Axboe
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=20090904175440.09a67ee7.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=jens.axboe@oracle$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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