From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/17] net: dsa: microchip: add error handling and register access validation
Date: Mon, 22 Aug 2022 18:49:40 -0700 [thread overview]
Message-ID: <20220822184940.125e7246@kernel.org> (raw)
In-Reply-To: <20220822110358.2310055-1-o.rempel@pengutronix.de>
On Mon, 22 Aug 2022 13:03:41 +0200 Oleksij Rempel wrote:
> changes v2:
> - add regmap_ranges for KSZ9477
> - drop output clock devicetree in driver validation patches. DTs need
> some more refactoring and can be done in a separate patch set.
> - remove some unused variables.
>
> This patch series adds error handling for the PHY read/write path and optional
> register access validation.
> After adding regmap_ranges for KSZ8563 some bugs was detected, so
> critical bug fixes are sorted before ragmap_range patch.
>
> Potentially this bug fixes can be ported to stable kernels, but need to be
> reworked.
This does not build in a fairly obvious way between patches 2 and 11 :(
Please make sure you do some form of a
git rebase --exec='make W=1 O=build_allmodconfig/'
where build_allmodconfig is a dir configured with make allmodconfig.
*Especially* when posting a large series.
prev parent reply other threads:[~2022-08-23 1:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 11:03 [PATCH net-next v2 00/17] net: dsa: microchip: add error handling and register access validation Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 01/17] net: dsa: microchip: add separate struct ksz_chip_data for KSZ8563 chip Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 02/17] net: dsa: microchip: do per-port Gbit detection instead of per-chip Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 03/17] net: dsa: microchip: don't announce extended register support on non Gbit chips Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 04/17] net: dsa: microchip: allow to pass return values for PHY read/write accesses Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 05/17] net: dsa: microchip: forward error value on all ksz_pread/ksz_pwrite functions Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 06/17] net: dsa: microchip: ksz9477: add error handling to ksz9477_r/w_phy Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 07/17] net: dsa: microchip: ksz8795: add error handling to ksz8_r/w_phy Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 08/17] net: dsa: microchip: KSZ9893: do not write to not supported Output Clock Control Register Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 09/17] net: dsa: microchip: add support for regmap_access_tables Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 10/17] net: dsa: microchip: add regmap_range for KSZ8563 chip Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 11/17] net: dsa: microchip: ksz9477: remove MII_CTRL1000 check from ksz9477_w_phy() Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 12/17] net: dsa: microchip: add regmap_range for KSZ9477 chip Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 13/17] net: dsa: microchip: ksz9477: use internal_phy instead of phy_port_cnt Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 14/17] net: dsa: microchip: remove unused port phy variable Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 15/17] net: dsa: microchip: ksz9477: remove unused "on" variable Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 16/17] net: dsa: microchip: remove unused sgmii variable Oleksij Rempel
2022-08-22 11:03 ` [PATCH net-next v2 17/17] net: dsa: microchip: remove IS_9893 flag Oleksij Rempel
2022-08-23 1:49 ` Jakub Kicinski [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=20220822184940.125e7246@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@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;
as well as URLs for NNTP newsgroup(s).