From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: Tom Musta <tommusta@gmail.com>, Alexander Graf <agraf@suse.de>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] target-ppc/translate.c: Use ULL suffix for 64 bit constants
Date: Thu, 20 Feb 2014 22:16:18 +0000 [thread overview]
Message-ID: <CAFEAcA8h2oe7W8dcNL_pO3n1SEpMYEDWBgkhTPft0mPea-xopQ@mail.gmail.com> (raw)
In-Reply-To: <530674B3.8050903@weilnetz.de>
On 20 February 2014 21:33, Stefan Weil <sw@weilnetz.de> wrote:
> (I personally prefer ULL instead of ull because it avoids constants
> ending with 'full', and if we ignore the disas code, ULL is also more
> common in QEMU)
I agree, as it happens, but I opted to stick with the existing case here.
thanks
-- PMM
next prev parent reply other threads:[~2014-02-20 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 19:47 [Qemu-devel] [PATCH] target-ppc/translate.c: Use ULL suffix for 64 bit constants Peter Maydell
2014-02-20 21:33 ` Stefan Weil
2014-02-20 22:16 ` Peter Maydell [this message]
2014-02-21 9:30 ` Alexander Graf
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=CAFEAcA8h2oe7W8dcNL_pO3n1SEpMYEDWBgkhTPft0mPea-xopQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sw@weilnetz.de \
--cc=tommusta@gmail.com \
/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).