All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Saenz Julienne <nsaenz@kernel.org>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Lee Jones" <lee.jones@linaro.org>,
	"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>,
	"kernel test robot" <lkp@intel.com>,
	"Linux PWM List" <linux-pwm@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pwm: raspberrypi-poe: Fix mailbox message initialization
Date: Fri, 9 Apr 2021 22:09:24 +0200	[thread overview]
Message-ID: <CAK8P3a3k94hJDJzCJSAC=jVF7S88vzUTK4V_cR31u0ve5jJJig@mail.gmail.com> (raw)
In-Reply-To: <20210409090819.24805-1-nsaenz@kernel.org>

On Fri, Apr 9, 2021 at 11:08 AM Nicolas Saenz Julienne
<nsaenz@kernel.org> wrote:
>
> For testing purposes this driver might be built on big-endian
> architectures. So make sure we take that into account when populating
> structures that are to be passed to RPi4's mailbox.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: 79caa362eab6 ("pwm: Add Raspberry Pi Firmware based PWM bus")
> Signed-off-by: Nicolas Saenz Julienne <nsaenz@kernel.org>
> ---
>
> @arndb: This was just meged into the arm-soc tree some days ago. Should I
> prepare a second PR once it's been reviewed?

Yes, that would be good. If you have no other driver patches that I should
pick up, just forward the patch (with the Ack) to soc@kernel.org and I
can just apply it.

        Arnd

      parent reply	other threads:[~2021-04-09 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  9:08 [PATCH] pwm: raspberrypi-poe: Fix mailbox message initialization Nicolas Saenz Julienne
2021-04-09 11:35 ` Thierry Reding
2021-04-09 20:09 ` Arnd Bergmann [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='CAK8P3a3k94hJDJzCJSAC=jVF7S88vzUTK4V_cR31u0ve5jJJig@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nsaenz@kernel.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.