All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: "Andreas Färber" <afaerber@suse.de>, qemu-trivial@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] libvixl: Fix format strings for several int64_t values
Date: Fri, 07 Mar 2014 21:01:11 +0100	[thread overview]
Message-ID: <531A2587.8030104@weilnetz.de> (raw)
In-Reply-To: <531A211D.8030209@suse.de>

Am 07.03.2014 20:42, schrieb Andreas Färber:
> Am 07.03.2014 20:15, schrieb Stefan Weil:
>> "%d" or "%x" won't work on hosts where int values are smaller than 64 bit.
>>
>> Signed-off-by: Stefan Weil <sw@weilnetz.de>
>> ---
>>  disas/libvixl/a64/disasm-a64.cc |   20 ++++++++++----------
>>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> Patch looks correct, but I see no indication that this is a backport
> from upstream libvixl. Have you submitted it there too?
> 
> Regards,
> Andreas


If I knew how to submit it to libvixl, I'd have done that already. I did
not find any hint (e-mail address, keyword contrib) in the sources from
github. Can you help me? It would also be fine if someone just takes my
patch and applies it there.

Thanks,
Stefan



WARNING: multiple messages have this Message-ID (diff)
From: Stefan Weil <sw@weilnetz.de>
To: "Andreas Färber" <afaerber@suse.de>, qemu-trivial@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] libvixl: Fix format strings for several int64_t values
Date: Fri, 07 Mar 2014 21:01:11 +0100	[thread overview]
Message-ID: <531A2587.8030104@weilnetz.de> (raw)
In-Reply-To: <531A211D.8030209@suse.de>

Am 07.03.2014 20:42, schrieb Andreas Färber:
> Am 07.03.2014 20:15, schrieb Stefan Weil:
>> "%d" or "%x" won't work on hosts where int values are smaller than 64 bit.
>>
>> Signed-off-by: Stefan Weil <sw@weilnetz.de>
>> ---
>>  disas/libvixl/a64/disasm-a64.cc |   20 ++++++++++----------
>>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> Patch looks correct, but I see no indication that this is a backport
> from upstream libvixl. Have you submitted it there too?
> 
> Regards,
> Andreas


If I knew how to submit it to libvixl, I'd have done that already. I did
not find any hint (e-mail address, keyword contrib) in the sources from
github. Can you help me? It would also be fine if someone just takes my
patch and applies it there.

Thanks,
Stefan

  reply	other threads:[~2014-03-07 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 19:15 [Qemu-trivial] [PATCH] libvixl: Fix format strings for several int64_t values Stefan Weil
2014-03-07 19:15 ` [Qemu-devel] " Stefan Weil
2014-03-07 19:42 ` [Qemu-trivial] " Andreas Färber
2014-03-07 19:42   ` Andreas Färber
2014-03-07 20:01   ` Stefan Weil [this message]
2014-03-07 20:01     ` Stefan Weil
2014-03-07 22:01     ` [Qemu-trivial] " Andreas Färber
2014-03-07 22:01       ` Andreas Färber
2014-03-10 14:20       ` [Qemu-trivial] " Peter Maydell
2014-03-10 14:20         ` Peter Maydell

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=531A2587.8030104@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=afaerber@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.