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] staging: greybus: authenticate: fix alignment and type warning
Date: Mon, 30 Mar 2026 17:52:47 +0200 [thread overview]
Message-ID: <2026033032-rethink-jogging-f3b0@gregkh> (raw)
In-Reply-To: <20260323031017.3650-1-k.souta0926@gmail.com>
On Mon, Mar 23, 2026 at 03:10:17AM +0000, Kosugi Souta wrote:
> Fix the following checkpatch.pl warning and check:
> - Warning: Prefer 'unsigned long long' over 'unsigned long long int'
> - Check: Alignment should match open parenthesis
That is two different things, so this should be two different patches,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-30 15:52 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 [this message]
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
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=2026033032-rethink-jogging-f3b0@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