qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-tricore: Add missing ULL suffix on 64 bit constant
Date: Mon, 19 Jan 2015 16:34:28 +0000	[thread overview]
Message-ID: <54BD3214.1020709@mail.uni-paderborn.de> (raw)
In-Reply-To: <CAFEAcA96172Mw2p=7t3oKWLgRFwzgLGh8LH6cNr1dWFp1Xog-Q@mail.gmail.com>


On 01/19/2015 03:21 PM, Peter Maydell wrote:
> On 24 December 2014 at 00:03, Bastian Koppelmann
> <kbastian@mail.uni-paderborn.de> wrote:
>> On 12/23/2014 10:24 PM, Peter Maydell wrote:
>>> Add a missing ULL suffix to a 64 bit constant: this suppresses a
>>> compiler warning from mingw32 gcc.
>>>
>>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>>> ---
>>>    target-tricore/op_helper.c | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>> Thanks, applied it to my tricore-next  branch.
> Ping?
Hi Peter,
> (I'm putting together a "miscellaneous stuff from me that's
> got forgotten" pull, so I could put it in that if you don't
> have any other tricore stuff queued and don't want to do a
> pullreq for a one line fix.)
thanks for the effort, but it is not forgotten. I'm still working on a 
patchset for the next pullreq. I'm sending the patchset to the list this 
week and depending on Richards feedback I will send a pullreq this or 
next week , but it is hard to tell. If this is too long for you, feel 
free to add your patch to the misc pull.

Cheers,
Bastian
> -- PMM

      reply	other threads:[~2015-01-19 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 22:24 [Qemu-devel] [PATCH] target-tricore: Add missing ULL suffix on 64 bit constant Peter Maydell
2014-12-24  0:03 ` Bastian Koppelmann
2015-01-19 15:21   ` Peter Maydell
2015-01-19 16:34     ` Bastian Koppelmann [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=54BD3214.1020709@mail.uni-paderborn.de \
    --to=kbastian@mail.uni-paderborn.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 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).