From: Linus Walleij <linus.walleij@linaro.org>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Ryan.Wanner@microchip.com, alexandre.belloni@bootlin.com,
linux-arm-kernel@lists.infradead.org, robh@kernel.org
Subject: Re: [PATCH] pinctrl: at91: fix deferred probing support
Date: Fri, 27 Jan 2023 13:49:11 +0100 [thread overview]
Message-ID: <CACRpkdZoGvV0SUGaJ=XYw5mEMx+p6FXsWLjUOsoz5=O=8Lq+nw@mail.gmail.com> (raw)
In-Reply-To: <e9aacc4f-4730-9b5f-8f00-ff10ecc4b222@microchip.com>
On Wed, Jan 25, 2023 at 12:35 PM Nicolas Ferre
<nicolas.ferre@microchip.com> wrote:
> > But I can apply it if it makes things better. Should I? Rob? Ludovic?
>
> Can you please apply this patch as I verified as well that it doesn't
> cause issues on a different SoC than Ryan:
>
> Tested-by: Nicolas Ferre <nicolas.ferre@microchip.com> # on sama5d3 xplained
> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
OK patch applied!
Yours,
Linus Walleij
_______________________________________________
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-27 13:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 19:22 [PATCH] pinctrl: at91: fix deferred probing support Rob Herring
2018-07-12 19:22 ` Rob Herring
2018-07-13 9:24 ` Ludovic Desroches
2018-07-13 9:24 ` Ludovic Desroches
2018-07-13 9:47 ` Alexandre Belloni
2018-07-13 9:47 ` Alexandre Belloni
2018-07-13 15:27 ` Rob Herring
2018-07-13 15:27 ` Rob Herring
2018-07-16 13:58 ` Linus Walleij
2018-07-16 13:58 ` Linus Walleij
2018-07-16 14:31 ` Rob Herring
2018-07-16 14:31 ` Rob Herring
2022-11-21 21:56 ` Ryan.Wanner
2022-11-22 8:32 ` Linus Walleij
2023-01-25 11:35 ` Nicolas Ferre
2023-01-27 12:49 ` Linus Walleij [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='CACRpkdZoGvV0SUGaJ=XYw5mEMx+p6FXsWLjUOsoz5=O=8Lq+nw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=Ryan.Wanner@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
/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.