mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@ieee.org>
To: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	outreachy@lists.linux.dev, johan@kernel.org, elder@kernel.org,
	gregkh@linuxfoundation.org, vaibhav.sr@gmail.com,
	mgreer@animalcreek.com, vireshk@kernel.org, rmfrfs@gmail.com,
	dtwlin@gmail.com, pure.logic@nexus-software.ie,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: Replace format specifiers
Date: Sat, 24 Oct 2026 09:14:00 -0500	[thread overview]
Message-ID: <3d919bc5-0fe0-4afc-a5fe-12c0ef1989dd@ieee.org> (raw)
In-Reply-To: <atuYWuWeqvEG6j4B@user>

On 10/23/26 12:24 PM, Yalagada Pavan Kumar wrote:
> On Thu, Oct 22, 2026 at 09:30:26AM -0400, Julia Lawall wrote:
>>
>> On Thu, 22 Oct 2026, Alex Elder wrote:
>>
>>> On 10/21/26 11:34 AM,pavankumaryalagada@gmail.com wrote:
>>>> From: Yalagada Pavan Kumar<pavankumaryalagada@gmail.com>
>>>>
>>>> Unsigned variables are printed using %d.
>>>> Replace them with %u to match their types.
>>>>
>>>> Signed-off-by: Yalagada Pavan Kumar<pavankumaryalagada@gmail.com>
>>> I have reviewed every one of these and they look good.  Quite a few
>>> of them--because the size of the value being formatted is less than
>>> 32 bits--would print correctly no matter what their value.  But I
>>> think it at least does no harm to convert the format specifier to
>>> unsigned in all of these cases.
>> I was suprised the compiler doesn't complain about this.  It seems to
>> complain a lot about type-related format specifiers.  Yalagada maybe it
>> could be worth adding something clearly invalid in one of the argument
>> lists to see if the code is actually getting compiled, or if you need to
>> set some config option to make that happen.
> The files compiled sucessfully with the normal build settings. I also
> enabled -Wformat-signedness to check for format mismatchse, as this check
> is not enabled by default. It revealed a few more issues, which i'll look
> into as well.

I think you might find that "sparse" complains.  Run your build
with "C=1" to run (by default) sparse, and see if it says something.

					-Alex

> 
> Pavan
> 
>> julia


  reply	other threads:[~2026-10-24 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 16:34 pavankumaryalagada
2026-10-22 13:16 ` Alex Elder
2026-10-22 13:30   ` Julia Lawall
2026-10-23 17:24     ` Yalagada Pavan Kumar
2026-10-24 14:14       ` Alex Elder [this message]
2026-10-22 13:35   ` Julia Lawall
2026-10-22 13:41     ` Alex Elder
2026-10-22 13:45       ` Julia Lawall
2026-10-22 13:52         ` Johan Hovold
2026-10-23  2:30           ` Bryan O'Donoghue

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=3d919bc5-0fe0-4afc-a5fe-12c0ef1989dd@ieee.org \
    --to=elder@ieee.org \
    --cc=dtwlin@gmail.com \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mgreer@animalcreek.com \
    --cc=outreachy@lists.linux.dev \
    --cc=pavankumaryalagada@gmail.com \
    --cc=pure.logic@nexus-software.ie \
    --cc=rmfrfs@gmail.com \
    --cc=vaibhav.sr@gmail.com \
    --cc=vireshk@kernel.org \
    /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

all inboxes | Powered by JetHome®