All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] clang -fsanitize=undefined warnings in the string visitors
Date: Thu, 5 Nov 2015 15:05:17 -0500	[thread overview]
Message-ID: <563BB67D.4070409@redhat.com> (raw)
In-Reply-To: <560D3739.1000405@redhat.com>



On 10/01/2015 09:38 AM, Paolo Bonzini wrote:
> 
> 
> On 01/10/2015 12:47, Peter Maydell wrote:
>> On 29 May 2015 at 12:12, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>
>>>
>>> On 29/05/2015 12:56, Peter Maydell wrote:
>>>>>>>> Paolo: ping^2, since we're out of release freeze now?
>>>>>>
>>>>>> I have some patches, but this isn't really the best time for me to post
>>>>>> them...
>>>> Ping...has the timing improved?
>>>
>>> Almost. :)  Next week, promised.
>>
>> Ping again, six months later...
> 
> Uh, I thought they were already in. :)
> 
> Paolo
> 

Did patches ever get posted to list for this?

--js

  reply	other threads:[~2015-11-05 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 23:17 [Qemu-devel] clang -fsanitize=undefined warnings in the string visitors Peter Maydell
2015-02-05 17:03 ` Peter Maydell
2015-05-11  8:53   ` Peter Maydell
2015-05-11  9:07     ` Paolo Bonzini
2015-05-29 10:56       ` Peter Maydell
2015-05-29 11:12         ` Paolo Bonzini
2015-10-01 10:47           ` Peter Maydell
2015-10-01 13:38             ` Paolo Bonzini
2015-11-05 20:05               ` John Snow [this message]
2016-01-14 11:15                 ` Peter Maydell
2016-01-14 12:44                   ` Paolo Bonzini
2016-01-14 12:52                     ` Peter Maydell
2015-10-01 14:58             ` Eric Blake

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=563BB67D.4070409@redhat.com \
    --to=jsnow@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --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 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.