From: Jani Nikula <jani.nikula@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
Aishwarya TCV <aishwarya.tcv@arm.com>
Subject: Re: [PATCH] drm/msm: convert all pixel format logging to use %p4cc
Date: Mon, 08 Apr 2024 11:09:38 +0300 [thread overview]
Message-ID: <87frvwb7i5.fsf@intel.com> (raw)
In-Reply-To: <eondf5x3wz3nccxpnqxtb7gtvf3k5u3bz4qwhn3gbcy5pj73ku@fue4tej3xgnq>
On Fri, 05 Apr 2024, Dmitry Baryshkov <dmitry.baryshkov@linaro.org> wrote:
> On Fri, Apr 05, 2024 at 12:29:07PM +0300, Jani Nikula wrote:
>> Logging u32 pixel formats using %4.4s format string with a pointer to
>> the u32 is somewhat questionable, as well as dependent on byte
>> order. There's a kernel extension format specifier %p4cc to format 4cc
>> codes. Use it across the board in msm for pixel format logging.
>>
>> This should also fix the reported build warning:
>>
>> include/drm/drm_print.h:536:35: warning: '%4.4s' directive argument is
>> null [-Wformat-overflow=]
>>
>> Reported-by: Aishwarya TCV <aishwarya.tcv@arm.com>
>> Closes: https://lore.kernel.org/r/2ac758ce-a196-4e89-a397-488ba31014c4@arm.com
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>
>> ---
>>
>> Tip: 'git show --color-words -w' might be the easiest way to review.
>> ---
>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 8 +++----
>> .../drm/msm/disp/dpu1/dpu_encoder_phys_wb.c | 2 +-
>> drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c | 4 ++--
>> drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 24 +++++++++----------
>> drivers/gpu/drm/msm/msm_fb.c | 10 ++++----
>> 5 files changed, 24 insertions(+), 24 deletions(-)
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Thanks! Do you take this via the msm tree?
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-04-08 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 9:29 [PATCH] drm/msm: convert all pixel format logging to use %p4cc Jani Nikula
2024-04-05 16:44 ` Dmitry Baryshkov
2024-04-08 8:09 ` Jani Nikula [this message]
2024-04-08 8:48 ` Dmitry Baryshkov
2024-04-08 9:57 ` Jani Nikula
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=87frvwb7i5.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=aishwarya.tcv@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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