From: Jakub Kicinski <kuba@kernel.org>
To: "M. Haener" <michael.haener@siemens.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
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>,
Russell King <linux@armlinux.org.uk>,
Alexander Sverdlin <alexander.sverdlin@siemens.com>
Subject: Re: [PATCH v2 0/3] net: dsa: SERDES support for mv88e632x family
Date: Wed, 5 Jul 2023 10:31:11 -0700 [thread overview]
Message-ID: <20230705103111.1a7fb88b@kernel.org> (raw)
In-Reply-To: <20230704065916.132486-1-michael.haener@siemens.com>
On Tue, 4 Jul 2023 08:59:03 +0200 M. Haener wrote:
> This patch series brings SERDES support for the mv88e632x family.
Not sure if this was said already - you'll need to repost once
Russell's patches are merged. It's a good practice to send patches
with unmet dependencies as RFC.
prev parent reply other threads:[~2023-07-05 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 6:59 [PATCH v2 0/3] net: dsa: SERDES support for mv88e632x family M. Haener
2023-07-04 6:59 ` [PATCH v2 1/3] net: dsa: mv88e632x: Refactor serdes read M. Haener
2023-07-04 7:23 ` Sverdlin, Alexander
2023-07-04 6:59 ` [PATCH v2 2/3] net: dsa: mv88e632x: Refactor serdes write M. Haener
2023-07-04 7:23 ` Sverdlin, Alexander
2023-07-04 6:59 ` [PATCH v2 3/3] net: dsa: mv88e632x: Add SERDES ops M. Haener
2023-07-04 7:23 ` Sverdlin, Alexander
2023-07-04 7:17 ` [PATCH v2 0/3] net: dsa: SERDES support for mv88e632x family Haener, Michael
2023-07-04 23:31 ` Andrew Lunn
2023-07-06 6:51 ` Haener, Michael
2023-07-13 6:42 ` Russell King (Oracle)
2023-07-13 7:41 ` Sverdlin, Alexander
2023-07-13 15:34 ` Andrew Lunn
2023-07-13 15:42 ` Russell King (Oracle)
2023-07-13 16:29 ` Sverdlin, Alexander
2023-07-13 19:33 ` Andrew Lunn
2023-07-14 8:07 ` Sverdlin, Alexander
2023-07-05 17:31 ` 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=20230705103111.1a7fb88b@kernel.org \
--to=kuba@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael.haener@siemens.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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).