Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Conor Dooley <conor@kernel.org>, linux-kernel@vger.kernel.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-riscv@lists.infradead.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org,
	Pierre-Henry Moussay <pierre-henry.moussay@microchip.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v3 3/3] dt-bindings: clock: mpfs-clkcfg: Add pic64gx compatibility
Date: Fri, 16 Jan 2026 08:53:27 +0200	[thread overview]
Message-ID: <6113b444-329e-455c-aeb9-71025746d44c@tuxon.dev> (raw)
In-Reply-To: <20260113-glue-justifier-566ffab2ffd3@spud>

Hi, Conor,

On 1/14/26 00:11, Conor Dooley wrote:
> From: Pierre-Henry Moussay <pierre-henry.moussay@microchip.com>
> 
> pic64gx has a clock controller compatible with mpfs-clkcfg. Don't permit
> the deprecated configuration that was never supported for this SoC.
> 
> Signed-off-by: Pierre-Henry Moussay <pierre-henry.moussay@microchip.com>
> Co-developed-by: Conor Dooley <conor.dooley@microchip.com>

 From Checkpatch:

WARNING: Co-developed-by: must be immediately followed by Signed-off-by:

I moved the Co-developed-by: tag before you SoB.

> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Reviewed-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>

Here.

Now, the full chain of trust is as follows:

     Signed-off-by: Pierre-Henry Moussay <pierre-henry.moussay@microchip.com>
     Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
     Reviewed-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
     Co-developed-by: Conor Dooley <conor.dooley@microchip.com>
     Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

Let me know you have anything against.

> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

Thank you,
Claudiu

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-01-16  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 22:11 [PATCH v3 0/3] pic64gx clk kconfig/binding changes Conor Dooley
2026-01-13 22:11 ` [PATCH v3 1/3] clk: microchip: drop POLARFIRE from ARCH_MICROCHIP_POLARFIRE Conor Dooley
2026-01-13 22:11 ` [PATCH v3 2/3] dt-bindings: clock: mpfs-ccc: Add pic64gx compatibility Conor Dooley
2026-01-13 22:11 ` [PATCH v3 3/3] dt-bindings: clock: mpfs-clkcfg: " Conor Dooley
2026-01-16  6:53   ` claudiu beznea [this message]
2026-01-16  6:53 ` [PATCH v3 0/3] pic64gx clk kconfig/binding changes claudiu beznea

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=6113b444-329e-455c-aeb9-71025746d44c@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=daire.mcnamara@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=pierre-henry.moussay@microchip.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox