From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Timo Alho <talho@nvidia.com>,
Manish Bhardwaj <mbhardwaj@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] firmware: tegra: bpmp: Prefer u32 over uint32_t
Date: Mon, 24 Oct 2022 15:18:56 +0200 [thread overview]
Message-ID: <Y1aQwBEuFvWSMi88@orome> (raw)
In-Reply-To: <20220922134125.844730-1-thierry.reding@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 458 bytes --]
On Thu, Sep 22, 2022 at 03:41:23PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The canonical type for 32-bit unsigned integers in the kernel is u32, so
> use that instead of uint32_t.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/firmware/tegra/bpmp-debugfs.c | 40 +++++++++++++--------------
> 1 file changed, 20 insertions(+), 20 deletions(-)
All three patches applied.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-24 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:41 [PATCH 1/3] firmware: tegra: bpmp: Prefer u32 over uint32_t Thierry Reding
2022-09-22 13:41 ` [PATCH 2/3] firmware: tegra: bpmp: Use iosys-map helpers Thierry Reding
2022-09-22 13:41 ` [PATCH 3/3] firmware: tegra: bpmp: Do not support big-endian Thierry Reding
2022-10-24 13:18 ` Thierry Reding [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=Y1aQwBEuFvWSMi88@orome \
--to=thierry.reding@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mbhardwaj@nvidia.com \
--cc=mperttunen@nvidia.com \
--cc=talho@nvidia.com \
/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