From: <Claudiu.Beznea@microchip.com>
To: <linus.walleij@linaro.org>
Cc: <Ludovic.Desroches@microchip.com>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] pinctrl: at91-pio4: few cleanups
Date: Thu, 9 Mar 2023 14:49:50 +0000 [thread overview]
Message-ID: <77c861d3-796b-e94b-08d4-a9c4e5980dbc@microchip.com> (raw)
In-Reply-To: <CACRpkda+D-U37LXBd_326gfJhUs+5meOcRH55PsCOEfmFVhBhg@mail.gmail.com>
On 07.03.2023 15:14, Linus Walleij wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Mar 2, 2023 at 12:01 PM Claudiu Beznea
> <claudiu.beznea@microchip.com> wrote:
>
>> Series contains few cleanups for pinctr-at91-pio4 driver.
>
> Patches applied, thank you Caludiu!
> I had to manually rebase patch 4 so check the result.
Looks good! Thank you, Linus!
Claudiu
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2023-03-09 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 11:01 Claudiu Beznea
2023-03-02 11:01 ` [PATCH 1/4] pinctrl: at91-pio4: use devm_clk_get_enabled() Claudiu Beznea
2023-03-02 11:01 ` [PATCH 2/4] pinctrl: at91-pio4: use device_get_match_data() Claudiu Beznea
2023-03-02 11:01 ` [PATCH 3/4] pinctrl: at91-pio4: use dev_err_probe() Claudiu Beznea
2023-03-02 11:01 ` [PATCH 4/4] pinctrl: at91-pio4: use proper format specifier for unsigned int Claudiu Beznea
2023-03-07 13:14 ` [PATCH 0/4] pinctrl: at91-pio4: few cleanups Linus Walleij
2023-03-09 14:49 ` Claudiu.Beznea [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=77c861d3-796b-e94b-08d4-a9c4e5980dbc@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®