From: Stephen Boyd <sboyd@kernel.org>
To: linux-clk@vger.kernel.org, mturquette@baylibre.com,
nicolas.ferre@microchip.com
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] clk: at91: clk for 5.17
Date: Thu, 09 Dec 2021 00:31:56 -0800 [thread overview]
Message-ID: <20211209083157.C0BAAC004DD@smtp.kernel.org> (raw)
In-Reply-To: <20211208133145.28267-1-nicolas.ferre@microchip.com>
Quoting nicolas.ferre@microchip.com (2021-12-08 05:31:45)
> From: Nicolas Ferre <nicolas.ferre@microchip.com>
>
> Stephen,
>
> Here are the clk changes for 5.17 which collect changes to the lan966x product
> line. We agreed to include these Microchip patches into the at91 branch with
> Kavyasree and Horatiu.
>
> Please pull.
>
> Thanks, best regards,
> Nicolas
>
> The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
>
> Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/clk-at91-5.17
>
> for you to fetch changes up to 5ad5915dea0047a6376d8f809ea3470ef68b1f92:
>
> clk: lan966x: Extend lan966x clock driver for clock gating support (2021-12-08 11:19:20 +0100)
>
> ----------------------------------------------------------------
Thanks. Pulled into clk-next
_______________________________________________
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:[~2021-12-09 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 13:31 [GIT PULL] clk: at91: clk for 5.17 nicolas.ferre
2021-12-09 8:31 ` Stephen Boyd [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=20211209083157.C0BAAC004DD@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=horatiu.vultur@microchip.com \
--cc=kavyasree.kotagiri@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=nicolas.ferre@microchip.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 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).