[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201011251830.40522.laurent.pinchart@ideasonboard.com>
Date: Thu, 25 Nov 2010 18:30:39 +0100
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Andy Walls <awalls@...metrocast.net>
Cc: Clemens Ladisch <clemens@...isch.de>, linux-media@...r.kernel.org,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
sakari.ailus@...well.research.nokia.com,
broonie@...nsource.wolfsonmicro.com, lennart@...ttering.net
Subject: Re: [RFC/PATCH v6 02/12] media: Media device
Hi Andy,
On Thursday 25 November 2010 18:20:31 Andy Walls wrote:
> The signedness of char is ambiguous for 8 bit data, which is why an API
> would normally use u8 (or s8, I guess).
>
> Since this is known to be character data, I would think char would be fine.
I think so too.
> I am assuming C compilers would never assume multibyte "char"s.
Not on sane platforms I guess. We would have problems much worse than MC API
breakage in that case anyway :-)
--
Regards,
Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists