From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: broonie@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, alexis.lothore@bootlin.com,
thomas.petazzoni@bootlin.com, andrew@lunn.ch,
edumazet@google.com, pabeni@redhat.com, f.fainelli@gmail.com,
hkallweit1@gmail.com, linux@armlinux.org.uk,
vladimir.oltean@nxp.com, ioana.ciornei@nxp.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, mcoquelin.stm32@gmail.com,
joabreu@synopsys.com, alexandre.torgue@foss.st.com,
peppe.cavallaro@st.com, simon.horman@corigine.com
Subject: Re: [PATCH net-next v4 0/4] net: add a regmap-based mdio driver and drop TSE PCS
Date: Mon, 5 Jun 2023 11:46:26 -0700 [thread overview]
Message-ID: <20230605114626.188c357f@kernel.org> (raw)
In-Reply-To: <20230605142039.3f8d1530@pc-7.home>
On Mon, 5 Jun 2023 14:20:39 +0200 Maxime Chevallier wrote:
> Thanks for applying the patch, however as mentionned (maybe not
> stressed enough in the cover) this series depends on a patch that went
> through the regmap tree :
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?id=e12ff28764937dd58c8613f16065da60da149048
>
> How can we proceed on that matter ?
I don't see a great solution, Mark already applied the change and
so did Dave. Don't think we can put them on stable branches now..
Only altera and stmmac-sogfpga are going to break?
Maybe we're close enough to the merge window to put our heads
in the sand and wait?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-05 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 14:14 [PATCH net-next v4 0/4] net: add a regmap-based mdio driver and drop TSE PCS Maxime Chevallier
2023-06-01 14:14 ` [PATCH net-next v4 1/4] net: mdio: Introduce a regmap-based mdio driver Maxime Chevallier
2023-06-05 7:37 ` Simon Horman
2023-06-01 14:14 ` [PATCH net-next v4 2/4] net: ethernet: altera-tse: Convert to mdio-regmap and use PCS Lynx Maxime Chevallier
2023-06-05 7:37 ` Simon Horman
2023-06-05 13:15 ` Maxime Chevallier
2023-06-01 14:14 ` [PATCH net-next v4 3/4] net: pcs: Drop the TSE PCS driver Maxime Chevallier
2023-06-01 14:14 ` [PATCH net-next v4 4/4] net: stmmac: dwmac-sogfpga: use the lynx pcs driver Maxime Chevallier
2023-06-05 7:38 ` Simon Horman
2023-06-05 10:30 ` [PATCH net-next v4 0/4] net: add a regmap-based mdio driver and drop TSE PCS patchwork-bot+netdevbpf
2023-06-05 12:20 ` Maxime Chevallier
2023-06-05 18:46 ` Jakub Kicinski [this message]
2023-06-06 6:39 ` Maxime Chevallier
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=20230605114626.188c357f@kernel.org \
--to=kuba@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=joabreu@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=simon.horman@corigine.com \
--cc=thomas.petazzoni@bootlin.com \
--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;
as well as URLs for NNTP newsgroup(s).