From: Greg KH <gregkh@linuxfoundation.org>
To: Prithvi Tambewagh <activprithvi@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, khalid@kernel.org
Subject: Re: [PATCH] staging: greybus: standardize data type and fix alignment to parentheses
Date: Sun, 8 Mar 2026 19:48:52 +0100 [thread overview]
Message-ID: <2026030840-linked-curliness-3f47@gregkh> (raw)
In-Reply-To: <20260301095154.144809-1-activprithvi@gmail.com>
On Sun, Mar 01, 2026 at 03:21:54PM +0530, Prithvi Tambewagh wrote:
> Standardize code in the file:
> drivers/staging/greybus/Documentation/firmware/authenticate.c
> by making the following changes:
>
> 1. Remove redundant 'int' from 'unsigned long long int' as suggested by
> checkpatch when printing the obtained device UID:
> printf("UID received: 0x%llx\n", *(unsigned long long *)(uid.uid));
>
> 2. Fix alignment of multi-line printf statement to match opening
> parentheses:
> printf("Authenticated, result (%02x), sig-size (%02x)\n",
> authenticate.result_code, authenticate.signature_size);
>
> Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
> ---
> drivers/staging/greybus/Documentation/firmware/authenticate.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/Documentation/firmware/authenticate.c b/drivers/staging/greybus/Documentation/firmware/authenticate.c
> index 3d2c6f88a138..ba4b16b04557 100644
> --- a/drivers/staging/greybus/Documentation/firmware/authenticate.c
> +++ b/drivers/staging/greybus/Documentation/firmware/authenticate.c
> @@ -58,7 +58,7 @@ int main(int argc, char *argv[])
> goto close_fd;
> }
>
> - printf("UID received: 0x%llx\n", *(unsigned long long int *)(uid.uid));
> + printf("UID received: 0x%llx\n", *(unsigned long long *)(uid.uid));
>
> /* Get certificate */
> printf("Get IMS certificate\n");
> @@ -85,7 +85,7 @@ int main(int argc, char *argv[])
> }
>
> printf("Authenticated, result (%02x), sig-size (%02x)\n",
> - authenticate.result_code, authenticate.signature_size);
> + authenticate.result_code, authenticate.signature_size);
>
> close_fd:
> close(fd);
>
> base-commit: eb71ab2bf72260054677e348498ba995a057c463
> --
> 2.34.1
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch did many different things all at once, making it difficult
to review. All Linux kernel patches need to only do one thing at a
time. If you need to do multiple things (such as clean up all coding
style issues in a file/driver), do it in a sequence of patches, each
one doing only one thing. This will make it easier to review the
patches to ensure that they are correct, and to help alleviate any
merge issues that larger patches can cause.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2026-03-08 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 9:51 [PATCH] staging: greybus: standardize data type and fix alignment to parentheses Prithvi Tambewagh
2026-03-08 18:48 ` Greg KH [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=2026030840-linked-curliness-3f47@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=activprithvi@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skhan@linuxfoundation.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