All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <mail@conchuod.ie>
To: Stephen Boyd <sboyd@kernel.org>,
	conor.dooley@microchip.com, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, mturquette@baylibre.com,
	robh+dt@kernel.org
Cc: krzysztof.kozlowski@canonical.com, geert@linux-m68k.org,
	david.abdurachmanov@gmail.com, palmer@dabbelt.com,
	daire.mcnamara@microchip.com, cyril.jean@microchip.com,
	Padmarao Begari <padmarao.begari@microchip.com>
Subject: Re: [PATCH v12 1/1] clk: microchip: Add driver for Microchip PolarFire SoC
Date: Sat, 12 Mar 2022 13:03:43 +0000	[thread overview]
Message-ID: <05e2fa13-163f-e6ef-4cf8-be6de513f068@conchuod.ie> (raw)
In-Reply-To: <20220312033230.5CB87C340E9@smtp.kernel.org>


On 12/03/2022 03:32, Stephen Boyd wrote:
> Quoting conor.dooley@microchip.com (2022-02-22 04:11:44)
>> From: Daire McNamara <daire.mcnamara@microchip.com>
>>
>> Add support for clock configuration on Microchip PolarFire SoC
>>
>> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>> Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
>> Co-developed-by: Padmarao Begari <padmarao.begari@microchip.com>
>> Signed-off-by: Padmarao Begari <padmarao.begari@microchip.com>
>> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
>> Co-developed-by: Conor Dooley <conor.dooley@microchip.com>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
> 
> Applied to clk-next

great, thanks!

      reply	other threads:[~2022-03-12 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 12:11 [PATCH v12 0/1] Add clkcfg driver for Microchip PolarFire SoC conor.dooley
2022-02-22 12:11 ` [PATCH v12 1/1] clk: microchip: Add " conor.dooley
2022-03-08  8:28   ` Conor.Dooley
2022-03-12  3:32   ` Stephen Boyd
2022-03-12 13:03     ` Conor Dooley [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=05e2fa13-163f-e6ef-4cf8-be6de513f068@conchuod.ie \
    --to=mail@conchuod.ie \
    --cc=conor.dooley@microchip.com \
    --cc=cyril.jean@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=david.abdurachmanov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=padmarao.begari@microchip.com \
    --cc=palmer@dabbelt.com \
    --cc=robh+dt@kernel.org \
    --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 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.