From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Avi Kivity <avi@qumranet•com>, Marcelo Tosatti <mtosatti@redhat•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Joerg Roedel <joerg.roedel@amd•com>
Subject: Re: linux-next: build failure after merge of the final tree (kvm tree related)
Date: Mon, 2 Aug 2010 10:33:50 +1000 [thread overview]
Message-ID: <20100802103350.9b1b8ff2.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100726142725.fbc5d94e.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Hi Avi, Marcelo,
On Mon, 26 Jul 2010 14:27:25 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the final tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
>
> cc1: warnings being treated as errors
> arch/powerpc/kvm/44x_tlb.c: In function 'kvmppc_mmu_map':
> arch/powerpc/kvm/44x_tlb.c:319: error: format '%lx' expects type 'long unsigned int', but argument 2 has type 'gfn_t'
>
> Caused by commit 05c07e00b15e00632a2502dcbf253415449e89da ("KVM: Use u64
> for frame data types"). I applied the following patch for today:
>
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Mon, 26 Jul 2010 14:25:12 +1000
> Subject: [PATCH] kvm: u64's should be printed with %llx
Ping?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-08-02 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 4:27 linux-next: build failure after merge of the final tree (kvm tree related) Stephen Rothwell
2010-08-02 0:33 ` Stephen Rothwell [this message]
2010-08-02 3:40 ` Avi Kivity
2010-08-02 4:25 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 3:28 Stephen Rothwell
2011-05-25 8:02 ` Heiko Carstens
2011-05-26 6:42 ` Avi Kivity
2011-02-21 6:56 Stephen Rothwell
2011-02-21 8:10 ` Huang Ying
2011-02-28 2:15 ` Stephen Rothwell
2011-02-28 2:28 ` Huang Ying
2011-02-28 9:36 ` Avi Kivity
2010-09-03 1:32 Stephen Rothwell
2010-04-07 6:40 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=20100802103350.9b1b8ff2.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=avi@qumranet$(echo .)com \
--cc=joerg.roedel@amd$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mtosatti@redhat$(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