public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Umang Jain <umang.jain@ideasonboard.com>,
	linux-staging@lists.linux.dev,
	linux-rpi-kernel@lists.infradead.org,
	linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Phil Elwell <phil@raspberrypi.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Dan Carpenter <error27@gmail.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	"Ricardo B . Marliere" <ricardo@marliere.net>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH 0/1] staging: vc04_services: Use %p4cc to print fourcc
Date: Wed, 25 Oct 2023 13:29:32 +0200	[thread overview]
Message-ID: <baa56840-8270-4d4e-aec5-2e6ccc8a9bc4@gmx.net> (raw)
In-Reply-To: <20231025060717.71895-1-umang.jain@ideasonboard.com>

Hi,

[add Raspberry Pi guys]

Am 25.10.23 um 08:07 schrieb Umang Jain:
> The following patch drop VCHIQ_FOURCC_AS_4CHARS macro in favour of %p4cc
> format modifier to print FourCC codes in the logs.
>
> *Before this patch*
> `mailbox: vchiq_core_msg debug: Sent Msg DATA(5) to AUDS s:1 d:62 len:20`
>
> *After this patch*
> bcm2835_vchiq 3f00b840.mailbox: vchiq_core_msg debug: Sent Msg DATA(5) to SDUA little-endian (0x41554453) s:1 d:62 len:20
>
> The inversion of AUDS to SDUA as per usage of %p4cc
> Does it hamper readability ? Feedback is appreciated.
looks good to me. Any concerns Phil or Dave?
>
> As documented in the commit message, the 'entity' char array length is
> increased to hold more characters for the log output. Not doing so,
> causes kernel stack corruption at runtime.
>
> Based on top of:
> - [PATCH v2 0/8] staging: vc04: Drop custom logging based on printk
>
> Umang Jain (1):
>    staging: vc04_services: Use %p4cc format modifier to print FourCC
>      codes
>
>   .../interface/vchiq_arm/vchiq_arm.c           | 20 +++++-----
>   .../interface/vchiq_arm/vchiq_core.c          | 40 +++++++++----------
>   .../interface/vchiq_arm/vchiq_core.h          |  6 ---
>   .../interface/vchiq_arm/vchiq_dev.c           |  7 ++--
>   4 files changed, 33 insertions(+), 40 deletions(-)
>


      parent reply	other threads:[~2023-10-25 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  6:07 [PATCH 0/1] staging: vc04_services: Use %p4cc to print fourcc Umang Jain
2023-10-25  6:07 ` [PATCH 1/1] staging: vc04_services: Use %p4cc format modifier to print FourCC codes Umang Jain
2023-10-25  7:10   ` Dan Carpenter
2023-10-25  9:28     ` Sakari Ailus
2023-10-25  9:34       ` Umang Jain
2023-10-25  9:46         ` Greg Kroah-Hartman
2023-10-25 11:12         ` Ricardo B. Marliere
2023-10-25 11:29 ` Stefan Wahren [this message]

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=baa56840-8270-4d4e-aec5-2e6ccc8a9bc4@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=phil@raspberrypi.com \
    --cc=ricardo@marliere.net \
    --cc=sakari.ailus@linux.intel.com \
    --cc=stefan.wahren@i2se.com \
    --cc=umang.jain@ideasonboard.com \
    /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