All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	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: Wed, 4 Jan 2023 13:57:23 +0100	[thread overview]
Message-ID: <20230104125723.p35aahg5nmckeke2@houat> (raw)
In-Reply-To: <622412ca-aee7-2e57-f9f6-3ff9871c5190@gmail.com>

Hi Florian,

On Tue, Jan 03, 2023 at 03:44:24PM -0800, Florian Fainelli wrote:
> On 1/2/23 03:52, Maxime Ripard 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>
> 
> As soon as v6.2-rc1 is cut, I will pick this up, thanks Maxime.

I'm not sure what you mean, we're at -rc2 already?

Maxime

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-01-04 13:44 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 [this message]
2023-01-10 21:44 ` Florian Fainelli

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=20230104125723.p35aahg5nmckeke2@houat \
    --to=maxime@cerno.tech \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=lkp@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.