From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Stephen Boyd <sboyd@kernel.org>, <linux-clk@vger.kernel.org>,
<mturquette@baylibre.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: Re: [GIT PULL] clk: at91: clk changes for 5.16
Date: Tue, 2 Nov 2021 11:57:10 +0100 [thread overview]
Message-ID: <23f15e48-319d-646d-5b7f-bd812be1d4b4@microchip.com> (raw)
In-Reply-To: <163529819030.15791.7009809622910069319@swboyd.mtv.corp.google.com>
Stephen,
On 27/10/2021 at 03:29, Stephen Boyd wrote:
> Quoting nicolas.ferre@microchip.com (2021-10-21 05:22:48)
>> From: Nicolas Ferre <nicolas.ferre@microchip.com>
>>
>> Stephen,
>>
>> Here are the clk changes for 5.16. I took the initiative to create a
>> Pull-Request for it as it's surely more convenient, as I proposed in my
>> reply to Claudiu's cover letter.
>
> Thanks. I didn't pick it up this time but I can pick it up next time. I
> wanted to take the clk.c patch via a different branch.
Perfect for me. I'll send Pull-Requests for at91 on the model of other
silicon vendors.
Don't hesitate to tell me if you want special arrangement for some of
the development cycles.
Best regards,
Nicolas
--
Nicolas Ferre
prev parent reply other threads:[~2021-11-02 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 12:22 [GIT PULL] clk: at91: clk changes for 5.16 nicolas.ferre
2021-10-27 1:29 ` Stephen Boyd
2021-11-02 10:57 ` Nicolas Ferre [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=23f15e48-319d-646d-5b7f-bd812be1d4b4@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).