[Qemu-devel] [PATCH] Fix build error in usb-ccid code

[Qemu-devel] [PATCH] Fix build error in usb-ccid code

[Dmitry Eremin-Solenikov]

W/o this fix I'm getting the following error:
cc1: warnings being treated as errors
hw/usb-ccid.c: In function ‘ccid_card_card_error’:
hw/usb-ccid.c:1202:5: error: format ‘%lX’ expects type ‘long unsigned int’, but argument 2 has type ‘uint64_t’

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
---
 hw/usb-ccid.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/hw/usb-ccid.c b/hw/usb-ccid.c
index 723b2e3..5c80cbd 100644
--- a/hw/usb-ccid.c
+++ b/hw/usb-ccid.c
@@ -1199,7 +1199,7 @@ void ccid_card_card_error(CCIDCardState *card, uint64_t error)
 
     s->bmCommandStatus = COMMAND_STATUS_FAILED;
     s->last_answer_error = error;
-    DPRINTF(s, 1, "VSC_Error: %lX\n", s->last_answer_error);
+    DPRINTF(s, 1, "VSC_Error: %LX\n", s->last_answer_error);
     /* TODO: these error's should be more verbose and propogated to the guest.*/
     /*
      * We flush all pending answers on CardRemove message in ccid-card-passthru,
-- 
1.7.4.1

Re: [Qemu-devel] [PATCH] Fix build error in usb-ccid code

[Peter Maydell]

On 4 April 2011 13:31, Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> wrote:
> W/o this fix I'm getting the following error:
> cc1: warnings being treated as errors
> hw/usb-ccid.c: In function ‘ccid_card_card_error’:
> hw/usb-ccid.c:1202:5: error: format ‘%lX’ expects type ‘long unsigned int’, but argument 2 has type ‘uint64_t’

David Gibson posted a patch for that earlier this morning:
http://patchwork.ozlabs.org/patch/89577/

-- PMM

Re: [Qemu-devel] [PATCH] Fix build error in usb-ccid code

[Dmitry Eremin-Solenikov]

On 4/4/11, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 4 April 2011 13:31, Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> wrote:
>> W/o this fix I'm getting the following error:
>> cc1: warnings being treated as errors
>> hw/usb-ccid.c: In function ‘ccid_card_card_error’:
>> hw/usb-ccid.c:1202:5: error: format ‘%lX’ expects type ‘long unsigned
>> int’, but argument 2 has type ‘uint64_t’
>
> David Gibson posted a patch for that earlier this morning:
> http://patchwork.ozlabs.org/patch/89577/

Sorry for the noise then.

-- 
With best wishes
Dmitry