All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>,
	alexandre.belloni@bootlin.com, conor.dooley@microchip.com,
	daire.mcnamara@microchip.com, mturquette@baylibre.com,
	nicolas.ferre@microchip.com
Cc: linux-clk@vger.kernel.org
Subject: Re: [GIT PULL] Microchip clock updates for 6.1
Date: Wed, 28 Sep 2022 16:20:35 -0700	[thread overview]
Message-ID: <20220928232037.468DAC4347C@smtp.kernel.org> (raw)
In-Reply-To: <20220915092927.4158755-1-claudiu.beznea@microchip.com>

Quoting Claudiu Beznea (2022-09-15 02:29:27)
> Hi, Stephen, Michael,
> 
> On Microchip we decided to send a single clock pull request for both
> AT91 and Polarfire architectures. Let us know if you would prefer otherwise.
> 
> Please note that this PR is based on Microchip clock fixes PR.
> 
> Thank you,
> Claudiu Beznea
> 
> The following changes since commit 05d27090b6dc88bce71a608d1271536e582b73d1:
> 
>   clk: microchip: mpfs: make the rtc's ahb clock critical (2022-09-14 10:45:52 +0300)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/clk-microchip-6.1
> 
> for you to fetch changes up to 935edf0c145596c26e7c6825918acde27ff94ff6:
> 
>   clk: at91: sama5d2: Add Generic Clocks for UART/USART (2022-09-15 11:01:37 +0300)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next

      reply	other threads:[~2022-09-28 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  9:29 [GIT PULL] Microchip clock updates for 6.1 Claudiu Beznea
2022-09-28 23:20 ` 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=20220928232037.468DAC4347C@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=linux-clk@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 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.