All of lore.kernel.org
 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: fix bug in mixeng_template.h build on NetBSD
Date: Mon, 14 May 2012 10:05:44 +0100	[thread overview]
Message-ID: <4FB0CAE8.7070709@citrix.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1205112300170.1508@linmac>

malc escribió:
> On Fri, 11 May 2012, Roger Pau Monne wrote:
>
>> This is a bug fix for rc1, although I think this bug has been present
>> for a long time.
>
> If there's a bug than it's within NetBSD itself, this issue has been
> discussed few times (at least twice it hink) in the past, please search
> the ML archives.
>
> [..snip..]
>

Hello,

I've found

http://copilotco.com/mail-archives/qemu.2008/msg11157.html

and

http://lists.gnu.org/archive/html/qemu-devel/2009-09/msg00255.html

But none of them seems to reach a conclusion about how to solve this. 
The standard regarding stdint.h doesn't forbid having this types defined 
as both typedefs and preprocessor macros, so I don't think this is a 
NetBSD bug. As far as I can see, we have at least three ways of solving 
this:

  - Undef the macros.
  - Use something like concat(conv_natural_, uint8_t, _to_mono) (as done 
on the second thread I've posted).
  - Pass two separate arguments; instead of using:

#define IN_T uint8_t

use something like:

#define BSIZE 8
#define ITYPE uint

But this will probably introduce quite some modifications.

Anyway, how do you think it's best to solve this?

Regards, Roger.

  reply	other threads:[~2012-05-14  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 12:20 [Qemu-devel] [PATCH] audio: fix bug in mixeng_template.h build on NetBSD Roger Pau Monne
2012-05-11 19:01 ` malc
2012-05-14  9:05   ` Roger Pau Monne [this message]
2012-05-14 20:51     ` malc

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=4FB0CAE8.7070709@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 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.