linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: alyssa@rosenzweig.io, Petr Mladek <pmladek@suse.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Sven Peter <sven@svenpeter.dev>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Aun-Ali Zaidi <admin@kodeit.net>,
	Maxime Ripard <mripard@kernel.org>,
	airlied@redhat.com, Simona Vetter <simona@ffwll.ch>,
	Steven Rostedt <rostedt@goodmis.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	apw@canonical.com, joe@perches.com, dwaipayanray1@gmail.com,
	lukas.bulwahn@gmail.com, tamird@gmail.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
	Hector Martin <marcan@marcan.st>,
	Asahi Linux Mailing List <asahi@lists.linux.dev>
Subject: Re: [PATCH v4 1/3] lib/vsprintf: Add support for generic FourCCs by extending %p4cc
Date: Tue, 8 Apr 2025 14:56:24 -0700	[thread overview]
Message-ID: <202504081456.31AF24D2F7@keescook> (raw)
In-Reply-To: <PN3PR01MB9597B01823415CB7FCD3BC27B8B52@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>

On Tue, Apr 08, 2025 at 12:17:57PM +0530, Aditya Garg wrote:
> From: Hector Martin <marcan@marcan.st>
> 
> %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 byte order
> %p4cn	Network byte order
> %p4cl	Little-endian
> %p4cb	Big-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. %p4cn would
> allow printing LSByte-first FourCCs stored in host endian order
> (other than the hex form being in character order, not the integer
> value).
> 
> Acked-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> Tested-by: Petr Mladek <pmladek@suse.com>
> Signed-off-by: Hector Martin <marcan@marcan.st>

Reviewed-by: Kees Cook <kees@kernel.org>

-- 
Kees Cook

  parent reply	other threads:[~2025-04-08 21:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  6:47 [PATCH v4 0/3] Use proper printk format in appletbdrm Aditya Garg
2025-04-08  6:47 ` [PATCH v4 1/3] lib/vsprintf: Add support for generic FourCCs by extending %p4cc Aditya Garg
2025-04-08  6:49   ` [PATCH v4 3/3] drm/appletbdrm: use %p4cl instead of %p4cc Aditya Garg
2025-04-08 21:56   ` Kees Cook [this message]
2025-04-22  8:07   ` [PATCH v4 1/3] lib/vsprintf: Add support for generic FourCCs by extending %p4cc Geert Uytterhoeven
2025-04-22  8:29     ` Aditya Garg
2025-04-22  8:43       ` Geert Uytterhoeven
2025-04-22  9:41         ` Aditya Garg
2025-04-22 10:16         ` Andy Shevchenko
2025-04-22 10:32           ` Geert Uytterhoeven
2025-04-22 15:15             ` Aditya Garg
2025-04-22 15:22               ` Andy Shevchenko
2025-04-22 15:28                 ` Aditya Garg
2025-04-22 15:17             ` Andy Shevchenko
2025-04-23 13:39         ` Petr Mladek
2025-04-23 13:47           ` Aditya Garg
2025-04-23 14:50           ` Geert Uytterhoeven
2025-04-23 16:29             ` Andy Shevchenko
2025-04-23 17:46               ` Geert Uytterhoeven
2025-04-22 10:12     ` Andy Shevchenko
2025-04-22 10:20       ` Geert Uytterhoeven
2025-04-08  6:48 ` [PATCH v4 2/3] printf: add tests for generic FourCCs Aditya Garg
2025-04-08 21:56   ` Kees Cook
2025-04-08  8:41 ` [PATCH v4 0/3] Use proper printk format in appletbdrm Andy Shevchenko
2025-04-08  8:52   ` Aditya Garg
2025-04-08  9:38     ` Andy Shevchenko
2025-04-09 15:30       ` Petr Mladek
2025-04-17 13:53 ` Aditya Garg
2025-04-21 12:05   ` Alyssa Rosenzweig
2025-04-21 13:05     ` Aditya Garg
2025-04-21 13:07       ` Alyssa Rosenzweig
2025-04-21 13:08         ` Aditya Garg
2025-04-21 13:10           ` Aditya Garg
2025-04-21 13:49             ` Alyssa Rosenzweig
2025-04-21 13:54               ` Aditya Garg
2025-04-21 13:56                 ` Alyssa Rosenzweig
2025-04-21 13:58                   ` Aditya Garg
2025-04-21 14:30 ` Alyssa Rosenzweig

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=202504081456.31AF24D2F7@keescook \
    --to=kees@kernel.org \
    --cc=admin@kodeit.net \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alyssa@rosenzweig.io \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=apw@canonical.com \
    --cc=asahi@lists.linux.dev \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dwaipayanray1@gmail.com \
    --cc=gargaditya08@live.com \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=lukas.bulwahn@gmail.com \
    --cc=marcan@marcan.st \
    --cc=mripard@kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=simona@ffwll.ch \
    --cc=sven@svenpeter.dev \
    --cc=tamird@gmail.com \
    --cc=tzimmermann@suse.de \
    /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).