From: Greg KH <gregkh@linuxfoundation.org>
To: Kosugi Souta <k.souta0926@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] staging: greybus: fix unsigned long long type warning
Date: Thu, 2 Apr 2026 07:33:46 +0200 [thread overview]
Message-ID: <2026040230-princess-okay-519f@gregkh> (raw)
In-Reply-To: <20260402051124.101197-2-k.souta0926@gmail.com>
On Thu, Apr 02, 2026 at 02:11:23PM +0900, Kosugi Souta wrote:
> Signed-off-by: Kosugi Souta <k.souta0926@gmail.com>
> ---
> drivers/staging/greybus/Documentation/firmware/authenticate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/greybus/Documentation/firmware/authenticate.c b/drivers/staging/greybus/Documentation/firmware/authenticate.c
> index 3d2c6f88a138a..0ef88b7d24de0 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");
> --
> 2.43.0
>
>
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:
- You did not specify a description of why the patch is needed, or
possibly, any description at all, in the email body. Please read the
section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what is needed in
order to properly describe the change.
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
next prev parent reply other threads:[~2026-04-02 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 3:10 [PATCH] staging: greybus: authenticate: fix alignment and type warning Kosugi Souta
2026-03-30 15:52 ` Greg KH
2026-04-02 5:11 ` [PATCH v2 0/2] staging: greybus: fix checkpatch style issues Kosugi Souta
2026-04-02 5:11 ` [PATCH v2 1/2] staging: greybus: fix unsigned long long type warning Kosugi Souta
2026-04-02 5:33 ` Greg KH [this message]
2026-04-02 5:11 ` [PATCH v2 2/2] staging: greybus: fix alignment to match open parenthesis Kosugi Souta
2026-04-04 0:59 ` [PATCH v3 0/2] staging: greybus: fix checkpatch style issues in authenticate.c Kosugi Souta
2026-04-04 0:59 ` [PATCH v3 1/2] staging: greybus: fix unsigned long long type warning Kosugi Souta
2026-04-04 0:59 ` [PATCH v3 2/2] staging: greybus: fix alignment to match open parenthesis Kosugi Souta
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=2026040230-princess-okay-519f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=k.souta0926@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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