Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753891Ab0KYRa3 (ORCPT ); Thu, 25 Nov 2010 12:30:29 -0500 Received: from perceval.ideasonboard.com ([95.142.166.194]:44548 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752179Ab0KYRa2 (ORCPT ); Thu, 25 Nov 2010 12:30:28 -0500 From: Laurent Pinchart To: Andy Walls Subject: Re: [RFC/PATCH v6 02/12] media: Media device Date: Thu, 25 Nov 2010 18:30:39 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r1; KDE/4.5.3; x86_64; ; ) Cc: Clemens Ladisch , linux-media@vger.kernel.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, sakari.ailus@maxwell.research.nokia.com, broonie@opensource.wolfsonmicro.com, lennart@poettering.net References: <1q7hf5w7lvslx3nba6ooh9j2.1290705631030@email.android.com> In-Reply-To: <1q7hf5w7lvslx3nba6ooh9j2.1290705631030@email.android.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201011251830.40522.laurent.pinchart@ideasonboard.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 24 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/