From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <olteanv@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
UNGLinuxDriver@microchip.com, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: dsa: microchip: add regmap_range for KSZ9563 chip
Date: Thu, 27 Jun 2024 15:00:32 -0700 [thread overview]
Message-ID: <20240627150032.7b97fc84@kernel.org> (raw)
In-Reply-To: <Zn1eeYwYgU2ocWHz@pengutronix.de>
On Thu, 27 Jun 2024 14:43:37 +0200 Oleksij Rempel wrote:
> Please ignore this patch, it was send by accident.
It fooled patchwork tho :(
--
pw-bot: cr
next prev parent reply other threads:[~2024-06-27 22:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 12:39 [PATCH net-next v1 1/1] net: dsa: microchip: add regmap_range for KSZ9563 chip Oleksij Rempel
2024-06-27 12:39 ` [PATCH net-next v1 1/3] net: dsa: microchip: lan9372: add 100BaseTX PHY support Oleksij Rempel
2024-06-28 2:31 ` Arun.Ramadoss
2024-06-27 12:39 ` [PATCH net-next v1 2/3] net: dsa: microchip: lan937x: force RGMII interface into PHY mode Oleksij Rempel
2024-06-27 15:15 ` Andrew Lunn
2024-06-27 22:25 ` Vladimir Oltean
2024-06-28 7:10 ` Oleksij Rempel
2024-06-28 14:02 ` Andrew Lunn
2024-06-27 12:39 ` [PATCH net-next v1 3/3] net: dsa: microchip: lan937x: disable VPHY output Oleksij Rempel
2024-06-27 22:38 ` Vladimir Oltean
2024-06-28 5:27 ` Oleksij Rempel
2024-06-28 8:45 ` Lucas Stach
2024-06-27 12:43 ` [PATCH net-next v1 1/1] net: dsa: microchip: add regmap_range for KSZ9563 chip Oleksij Rempel
2024-06-27 22:00 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-08 10:50 Oleksij Rempel
2024-03-11 9:21 ` Simon Horman
2024-03-11 16:36 ` Florian Fainelli
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=20240627150032.7b97fc84@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.