LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>, Vinod Koul <vkoul@kernel.org>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	Ioana Ciornei <ioana.ciornei@nxp.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Tanjeff Moos <tanjeff.moos@westermo.com>,
	Michael Walle <mwalle@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4 phy-next 0/9] RCW override for 10G Lynx dynamic protocol reconfiguration
Date: Tue, 28 Jul 2026 17:30:06 +0200	[thread overview]
Message-ID: <5306f685-46df-4956-9402-a86834f913c7@kernel.org> (raw)
In-Reply-To: <20260728134746.p7zqstau6376xifj@skbuf>

Hi Oltean,

Le 28/07/2026 à 15:47, Vladimir Oltean a écrit :
> Hi Christophe,
> 
> On Thu, Jul 23, 2026 at 06:01:05PM +0300, Vladimir Oltean wrote:
>> On Wed, Jul 22, 2026 at 02:15:54AM +0300, Vladimir Oltean wrote:
>>> Ioana Ciornei (4):
>>>    soc: fsl: guts: use a macro to encode the DCFG CCSR space
>>>    soc: fsl: guts: add a global structure to hold state
>>>    soc: fsl: guts: add a central fsl_guts_read() function
>>>    soc: fsl: guts: make it easier to determine on which SoC we are
>>>      running
>>>
>>> Vladimir Oltean (5):
>>>    soc: fsl: guts: perform fsl_guts_init() error teardown in reverse
>>>      order of setup
>>>    soc: fsl: guts: make fsl_soc_data available after fsl_guts_init()
>>>    dt-bindings: fsl: layerscape-dcfg: define DCFG_DCSR region
>>>    soc: fsl: guts: implement the RCW override procedure
>>>    phy: lynx-10g: use RCW override procedure for dynamic protocol change
>>
>> Even though I intended these changes for linux-phy (they are also
>> build-tested there), I'm fine either with these changes taken through
>> Vinod's tree with Christophe's ACK for patches 1-8, or through
>> Christophe's tree with Vinod's ACK for patch 9, really.
>>
>> I see on Patchwork there's a minor issue in the commit message of patch 3/9:
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fproject%2Flinux-phy%2Fpatch%2F20260721231603.67865-4-vladimir.oltean%40nxp.com%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7Cdfcaa68452fc46a3285108deecaed436%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C639208432793851204%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=AUY%2BIZEiFp3aLAO4HlHQCrJ9ZnCyFqzshPEGq6CpfmU%3D&reserved=0
>> "WARNING: 'struture' may be misspelled - perhaps 'structure'?"
>>
>> Could this be fixed up while applying, if there is no other feedback?
> 
> Do you have feedback/a preference for how these patches should be handled?
> 
> I see Vinod acked patch 9, so I guess that means his preference would be
> for you to pick up the entire series (which is indivisible).
> 
> I checked that the patches apply to your soc_fsl branch:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fchleroy%2Flinux.git%2F%3Fh%3Dsoc_fsl&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7Cdfcaa68452fc46a3285108deecaed436%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C639208432793877128%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xjpwRCMIncWpW89zKzhil20%2BcUhnG4LPaFNbxw1pue8%3D&reserved=0
> 

Hum ... Seems like I overlooked your message as it was flagged phy-next 
and I was on summer vacation on last two weeks.

I'm fine with taking them via soc_fsl tree. I won't take them today 
because I'm already pushing a large series from Paul Louvel but I'd push 
them by tomorrow or thurday.

Please raise hand if nothing happened by friday.

Christophe


      reply	other threads:[~2026-07-28 15:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 23:15 [PATCH v4 phy-next 0/9] RCW override for 10G Lynx dynamic protocol reconfiguration Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 1/9] soc: fsl: guts: perform fsl_guts_init() error teardown in reverse order of setup Vladimir Oltean
2026-07-22  7:18   ` Michael Walle
2026-07-22  7:55     ` Vladimir Oltean
2026-07-22  9:15   ` Ioana Ciornei
2026-07-21 23:15 ` [PATCH v4 phy-next 2/9] soc: fsl: guts: use a macro to encode the DCFG CCSR space Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 3/9] soc: fsl: guts: add a global structure to hold state Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 4/9] soc: fsl: guts: add a central fsl_guts_read() function Vladimir Oltean
2026-07-21 23:15 ` [PATCH v4 phy-next 5/9] soc: fsl: guts: make it easier to determine on which SoC we are running Vladimir Oltean
2026-07-21 23:16 ` [PATCH v4 phy-next 6/9] soc: fsl: guts: make fsl_soc_data available after fsl_guts_init() Vladimir Oltean
2026-07-22  9:19   ` Ioana Ciornei
2026-07-21 23:16 ` [PATCH v4 phy-next 7/9] dt-bindings: fsl: layerscape-dcfg: define DCFG_DCSR region Vladimir Oltean
2026-07-21 23:16 ` [PATCH v4 phy-next 8/9] soc: fsl: guts: implement the RCW override procedure Vladimir Oltean
2026-07-22 11:01   ` Ioana Ciornei
2026-07-21 23:16 ` [PATCH v4 phy-next 9/9] phy: lynx-10g: use RCW override procedure for dynamic protocol change Vladimir Oltean
2026-07-22 11:03   ` Ioana Ciornei
2026-07-24  6:00   ` Vinod Koul
2026-07-23 15:01 ` [PATCH v4 phy-next 0/9] RCW override for 10G Lynx dynamic protocol reconfiguration Vladimir Oltean
2026-07-28 13:47   ` Vladimir Oltean
2026-07-28 15:30     ` Christophe Leroy (CS GROUP) [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=5306f685-46df-4956-9402-a86834f913c7@kernel.org \
    --to=chleroy@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mwalle@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=tanjeff.moos@westermo.com \
    --cc=vkoul@kernel.org \
    --cc=vladimir.oltean@nxp.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