qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: malc <av1474@comtv.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] audio: split IN_T into two separate constants
Date: Fri, 18 May 2012 14:11:40 +0100	[thread overview]
Message-ID: <4FB64A8C.4070006@citrix.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1205181528030.2782@linmac>

malc wrote:
> On Fri, 18 May 2012, Roger Pau Monne wrote:
>
>> Split IN_T into BSIZE and ITYPE, to avoid expansion if the OS has
>> defined macros for the intX_t and uintX_t types. The IN_T constant is
>> then defined in mixeng_template.h so it can be used by the
>> functions/macros on this header file.
>>
>> This change has been tested successfully under Debian Linux and NetBSD
>> 6.0BETA.
>>
>
> Applied.

Thanks!

      reply	other threads:[~2012-05-18 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 11:08 [Qemu-devel] [PATCH] audio: split IN_T into two separate constants Roger Pau Monne
2012-05-18 11:28 ` malc
2012-05-18 13:11   ` Roger Pau Monne [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=4FB64A8C.4070006@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=av1474@comtv.ru \
    --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).