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>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] clk: at91: clk for 5.18
Date: Wed, 09 Mar 2022 10:17:49 -0800 [thread overview]
Message-ID: <20220309181753.8CA0CC340E8@smtp.kernel.org> (raw)
In-Reply-To: <20220308152657.30651-1-nicolas.ferre@microchip.com>
Quoting nicolas.ferre@microchip.com (2022-03-08 07:26:57)
> From: Nicolas Ferre <nicolas.ferre@microchip.com>
>
> Stephen,
>
> Here are a couple more clk changes for 5.18. This Pull-Request is made on top
> of what you already have for at91 targeting 5.18 on your clk-at91 existing
> branch. Hopefully, we are aligned on this.
> this.
>
> Please pull.
>
> Thanks, best regards,
> Nicolas
>
> The following changes since commit a5ab04af49434aef532bf6cd4baa08a13665d608:
>
> clk: at91: sama7g5: Allow MCK1 to be exported and referenced in DT (2022-01-24 17:05:45 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/clk-at91-5.18
>
> for you to fetch changes up to 8e842f02af7e2f6225d52d78cd25b465a98d344b:
>
> clk: at91: clk-master: remove dead code (2022-03-08 15:37:08 +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:[~2022-03-09 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 15:26 [GIT PULL] clk: at91: clk for 5.18 nicolas.ferre
2022-03-09 18:17 ` 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=20220309181753.8CA0CC340E8@smtp.kernel.org \
--to=sboyd@kernel.org \
--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=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).