From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Mihai Sain <mihai.sain@microchip.com>,
mturquette@baylibre.com, sboyd@kernel.org,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
varshini.rajendran@microchip.com, cristian.birsan@microchip.com,
balamanikandan.gunasundar@microchip.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
ryan.wanner@microchip.com
Subject: Re: [PATCH 3/4] clk: at91: sam9x7: Fix gmac_gclk clock definition
Date: Sun, 8 Mar 2026 18:12:07 +0200 [thread overview]
Message-ID: <7de6368c-0b9b-46dd-a752-e063f88ae164@tuxon.dev> (raw)
In-Reply-To: <20260302142008.3253-4-mihai.sain@microchip.com>
Hi, Mihai,
On 3/2/26 16:20, Mihai Sain wrote:
> According with datasheet [1] table 12.1 the instance ID 24 is used
> for gmac generic clock.
> This patch adds the correct gmac_gclk entry at ID 24, aligned with the
> SoC clock layout, and removes the old misplaced 67 entry.
>
Something is wrong with this patch and the next one. I suppose it's the missing
version number in title as I cannot grab it with b4. Can you please re-send?
Thank you,
Claudiu
next prev parent reply other threads:[~2026-03-08 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:20 [PATCH v3 0/4] Update gmac clocks and devicetree for sam9x7 mpu Mihai Sain
2026-03-02 14:20 ` [PATCH v3 1/4] clk: at91: sam9x7: Remove gmac peripheral clock with ID 67 Mihai Sain
2026-03-02 14:20 ` [PATCH v3 2/4] clk: at91: sam9x7: Rename macb0_clk to gmac_clk Mihai Sain
2026-03-02 14:20 ` [PATCH 3/4] clk: at91: sam9x7: Fix gmac_gclk clock definition Mihai Sain
2026-03-08 16:12 ` Claudiu Beznea [this message]
2026-03-02 14:20 ` [PATCH 4/4] ARM: dts: microchip: sam9x7: fix GMAC clock configuration Mihai Sain
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=7de6368c-0b9b-46dd-a752-e063f88ae164@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=balamanikandan.gunasundar@microchip.com \
--cc=conor+dt@kernel.org \
--cc=cristian.birsan@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=ryan.wanner@microchip.com \
--cc=sboyd@kernel.org \
--cc=varshini.rajendran@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