From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 025C2C433FE for ; Tue, 22 Nov 2022 12:44:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=bbwPFCYgRQ2BgAYRHs/rgSY0e5utBPtX0VCzH6uadE8=; b=gOX3qvDG3KLIIr Qx2WGXqlHovkPdaHSUWcf93wQ0TRsPvOlcnRzmD75u3xCN6/Ejaf7vCzoNDnebePOgSbrmoQ78Q0v 2EWPoHJj0tA81Sb84AIfte1GtMajLW/DAR1qEilRD31+bJmKJyRLxLGyCbcZQ1drxWTz4sTVgaVlK vxUGVEVXu1hoaxO5bHy4Jv9LWP6EOfKfxnBhUGjBjiFUouG8MfxGMWkDmFi+KPYJ7gfGjn1WbkPaF PJlSbwEgh6ednufpzfEjgBmpE5RrnXaH0rkh4j7P9iMy19Cwpk0Tkj0HfuhabHKv5B1AdiGQy6rbe o70IgH0qPgRNjbI+7Viw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oxScj-009KTy-70; Tue, 22 Nov 2022 12:43:37 +0000 Received: from smtp-out2.suse.de ([2001:67c:2178:6::1d]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oxScf-009KMc-55 for linux-arm-kernel@lists.infradead.org; Tue, 22 Nov 2022 12:43:35 +0000 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 6CD801F86C; Tue, 22 Nov 2022 12:43:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1669121009; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+LttO4rwpoEUKx+mKrlRotB9foBpDXaTdB6zGT0DKgM=; b=ECk0gdBvt1mE2jQiltgYhsFiQNQPIPXHcekRdV1hpQDSitwE3iuuWa2Nl+Yuv4JL+Xb7qX wgSOiTlj8GL42umxGL1Ajp3XsnlksRR9pDJV92RYvqEHo1At21rVmtPN7zv9gZ3FI/qxdB 0bICCWaFXg9/uyIBG8u7x6+OEwXd3k8= Received: from suse.cz (unknown [10.100.201.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id C30942C142; Tue, 22 Nov 2022 12:43:28 +0000 (UTC) Date: Tue, 22 Nov 2022 13:43:28 +0100 From: Petr Mladek To: "Russell King (Oracle)" Cc: Linus Walleij , Bartosz Golaszewski , Rob Herring , Lee Jones , Alyssa Rosenzweig , Andy Shevchenko , asahi@lists.linux.dev, devicetree@vger.kernel.org, Hector Martin , Jonathan Corbet , Krzysztof Kozlowski , linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, linux-gpio@vger.kernel.org, Rasmus Villemoes , Sergey Senozhatsky , Steven Rostedt , Sven Peter Subject: Re: [PATCH v3 2/7] lib/vsprintf: Add support for generic FOURCCs by extending %p4cc Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221122_044333_395443_3895952E X-CRM114-Status: GOOD ( 30.05 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon 2022-11-14 16:15:50, Russell King (Oracle) wrote: > On Mon, Nov 14, 2022 at 04:34:07PM +0100, Petr Mladek wrote: > > On Tue 2022-11-08 16:33:22, Russell King wrote: > > > From: Hector Martin > > > > > > %p4cc is designed for DRM/V4L2 FOURCCs with their specific quirks, but > > > it's useful to be able to print generic 4-character codes formatted as > > > an integer. Extend it to add format specifiers for printing generic > > > 32-bit FOURCCs with various endian semantics: > > > > > > %p4ch Host-endian > > > %p4cl Little-endian > > > %p4cb Big-endian > > > %p4cr Reverse-endian > > > > > > The endianness determines how bytes are interpreted as a u32, and the > > > FOURCC is then always printed MSByte-first (this is the opposite of > > > V4L/DRM FOURCCs). This covers most practical cases, e.g. %p4cr would > > > allow printing LSByte-first FOURCCs stored in host endian order > > > (other than the hex form being in character order, not the integer > > > value). > > > > > > Signed-off-by: Hector Martin > > > Signed-off-by: Russell King (Oracle) > > > > Reviewed-by: Petr Mladek > > > > See one nit below. > > > > > --- a/lib/vsprintf.c > > > +++ b/lib/vsprintf.c > > > @@ -1762,27 +1762,50 @@ char *fourcc_string(char *buf, char *end, const u32 *fourcc, > > > char output[sizeof("0123 little-endian (0x01234567)")]; > > > char *p = output; > > > unsigned int i; > > > + bool pixel_fmt = false; > > > u32 orig, val; > > > > > > - if (fmt[1] != 'c' || fmt[2] != 'c') > > > + if (fmt[1] != 'c') > > > return error_string(buf, end, "(%p4?)", spec); > > > > > > if (check_pointer(&buf, end, fourcc, spec)) > > > return buf; > > > > > > orig = get_unaligned(fourcc); > > > - val = orig & ~BIT(31); > > > + switch (fmt[2]) { > > > + case 'h': > > > + val = orig; > > > + break; > > > + case 'r': > > > + val = orig = swab32(orig); > > > > I do not like much these multi assignments. I think that the result > > was not even defined in some older C standards. Though, I can't find > > it now. And even make W=3 does not warn about it. > > Err. > > It's been supported for decades. I learnt about it back in 1992 when > I was introduced to C by another experienced C programmer. It's been > supported in ANSI C compilers. The Norcroft C compiler (which is > strict ANSI) on Acorn platforms back in the late 1980s/1990s even > supported it. Ah, the problem probably was with a more complicated assignment. For example, the result of the following code is not obvious: a = b = a++; Best Regards, Petr _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel