From: liubo <liubo2009@cn.fujitsu.com>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix compile warning in fs/btrfs/inode.c
Date: Thu, 09 Dec 2010 09:08:18 +0800 [thread overview]
Message-ID: <4D002C02.20105@cn.fujitsu.com> (raw)
In-Reply-To: <4CFF576E.8030505@cn.fujitsu.com>
On 12/08/2010 06:01 PM, liubo wrote:
> While compiling btrfs, I got belows:
>=20
> CC [M] fs/btrfs/inode.o
> fs/btrfs/inode.c: In function =E2=80=98btrfs_end_dio_bio=E2=80=99:
> fs/btrfs/inode.c:5720: warning: format =E2=80=98%lu=E2=80=99 expects =
type =E2=80=98long unsigned int=E2=80=99, but argument 4 has type =E2=80=
=98sector_t=E2=80=99
> LD [M] fs/btrfs/btrfs.o
> Building modules, stage 2.
> MODPOST 1 modules
> LD [M] fs/btrfs/btrfs.ko
>=20
> This fixes the compile warning.
>=20
Sorry, plz ignore this.
Have seen someone post patch to fix this.
thanks,
Liu Bo
> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
> ---
> fs/btrfs/inode.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>=20
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 0f34cae..eff5aef 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -5713,8 +5713,8 @@ static void btrfs_end_dio_bio(struct bio *bio, =
int err)
> if (err) {
> printk(KERN_ERR "btrfs direct IO failed ino %lu rw %lu "
> "disk_bytenr %lu len %u err no %d\n",
> - dip->inode->i_ino, bio->bi_rw, bio->bi_sector,
> - bio->bi_size, err);
> + dip->inode->i_ino, bio->bi_rw,
> + (unsigned long)bio->bi_sector, bio->bi_size, err);
> dip->errors =3D 1;
> =20
> /*
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-12-09 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 10:01 [PATCH] Btrfs: fix compile warning in fs/btrfs/inode.c liubo
2010-12-08 23:59 ` Tsutomu Itoh
2010-12-09 1:08 ` liubo [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=4D002C02.20105@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
/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).