qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org
Cc: Stefan Weil <sw@weilnetz.de>
Subject: Re: [PATCH v5 0/2] util/oslib: qemu_try_memalign() improvements
Date: Tue, 5 Jan 2021 10:56:02 +0100	[thread overview]
Message-ID: <522044f0-04a9-0298-5e48-308765e30a1a@redhat.com> (raw)
In-Reply-To: <8d2d61a4-5102-bd93-b057-870eb6e805ef@linaro.org>

On 05/01/21 01:06, Richard Henderson wrote:
> On 12/16/20 9:24 AM, Richard Henderson wrote:
>> On 10/21/20 12:38 PM, Philippe Mathieu-Daudé wrote:
>>> - Use _aligned_malloc for qemu_try_memalign on win32
>>> - Assert qemu_try_memalign() alignment is a power of 2
>>>
>>> Since v4:
>>> - Drop superfluous assert (Richard)
>>>
>>> Philippe Mathieu-Daudé (1):
>>>    util/oslib: Assert qemu_try_memalign() alignment is a power of 2
>>>
>>> Richard Henderson (1):
>>>    util/oslib-win32: Use _aligned_malloc for qemu_try_memalign
>>>
>>>   util/oslib-posix.c |  2 ++
>>>   util/oslib-win32.c | 12 +++++-------
>>>   2 files changed, 7 insertions(+), 7 deletions(-)
>>>
>>
>> Ping.
> 
> Ping2.  Shall I just queue this to tcg-next?

Yes, just go ahead.  util/ is everybody's land, maintainers are supposed 
to know what they're doing. :)

Paolo



      reply	other threads:[~2021-01-05 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 17:38 [PATCH v5 0/2] util/oslib: qemu_try_memalign() improvements Philippe Mathieu-Daudé
2020-10-21 17:38 ` [PATCH v5 1/2] util/oslib-win32: Use _aligned_malloc for qemu_try_memalign Philippe Mathieu-Daudé
2020-10-21 17:38 ` [PATCH v5 2/2] util/oslib: Assert qemu_try_memalign() alignment is a power of 2 Philippe Mathieu-Daudé
2020-12-16 19:24 ` [PATCH v5 0/2] util/oslib: qemu_try_memalign() improvements Richard Henderson
2021-01-05  0:06   ` Richard Henderson
2021-01-05  9:56     ` Paolo Bonzini [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=522044f0-04a9-0298-5e48-308765e30a1a@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sw@weilnetz.de \
    /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).