From: Vladimir Oltean <olteanv@gmail.com>
To: Michael Walle <mwalle@kernel.org>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
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>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Tanjeff Moos <tanjeff.moos@westermo.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Frank Li <Frank.Li@nxp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 phy-next 1/9] soc: fsl: guts: perform fsl_guts_init() error teardown in reverse order of setup
Date: Wed, 22 Jul 2026 10:55:42 +0300 [thread overview]
Message-ID: <20260722075542.p3uissyqzcvfsdri@skbuf> (raw)
In-Reply-To: <DK4X0XV6ZM1E.2L9G007WXO2J6@kernel.org>
On Wed, Jul 22, 2026 at 09:18:48AM +0200, Michael Walle wrote:
> Hi,
>
> On Wed Jul 22, 2026 at 1:15 AM CEST, Vladimir Oltean wrote:
> > Michael Walle has confirmed that ignoring the error was intentional,
> > and we preserve that:
> > https://lore.kernel.org/linux-phy/DK44809N7Y8I.J2Z3U4N32H0Q@kernel.org/
>
> I thought you wanted to check if kasprintf() fails and return an
> error? Just to be clear, I'm fine with either way.
I did, but then I considered I don't have a strong justification, and it
isn't a change I need to make to make progress with this series, rather
more of a distraction.
next prev parent reply other threads:[~2026-07-22 7:55 UTC|newest]
Thread overview: 16+ 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 [this message]
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
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=20260722075542.p3uissyqzcvfsdri@skbuf \
--to=olteanv@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=chleroy@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--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=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