From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
Maxime Ripard <maxime@cerno.tech>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH RESEND] firmware: raspberrypi: Fix type assignment
Date: Tue, 10 Jan 2023 13:44:05 -0800 [thread overview]
Message-ID: <20230110214405.1006458-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20230102115255.17802-1-maxime@cerno.tech>
On Mon, 2 Jan 2023 12:52:55 +0100, Maxime Ripard <maxime@cerno.tech> wrote:
> We silently cast an unsigned int into a __le32 which makes sparse
> complain. Moreover, we never actually convert endianness between the
> CPU's and the expected little-endian value. Fix both at once by calling
> cpu_to_le32().
>
> Fixes: 40c31955e4e9 ("firmware: raspberrypi: Provide a helper to query a clock max rate")
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/r/20221116091712.1309651-3-maxime@cerno.tech
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/drivers/fixes, thanks!
--
Florian
_______________________________________________
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:[~2023-01-10 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 11:52 [PATCH RESEND] firmware: raspberrypi: Fix type assignment Maxime Ripard
2023-01-03 23:44 ` Florian Fainelli
2023-01-04 12:57 ` Maxime Ripard
2023-01-10 21:44 ` Florian Fainelli [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=20230110214405.1006458-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=maxime@cerno.tech \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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;
as well as URLs for NNTP newsgroup(s).