From: "Haener, Michael" <michael.haener@siemens.com>
To: "andrew@lunn.ch" <andrew@lunn.ch>
Cc: "olteanv@gmail.com" <olteanv@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Sverdlin, Alexander" <alexander.sverdlin@siemens.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>
Subject: Re: [PATCH 0/3] net: dsa: SERDES support for mv88e632x family
Date: Tue, 4 Jul 2023 06:11:26 +0000 [thread overview]
Message-ID: <3322f0995be4b49bcc349d7a58ec9114fca6c3f9.camel@siemens.com> (raw)
In-Reply-To: <3664909e-a259-4bca-be53-5bab43e23dbc@lunn.ch>
Thanks for your message. I will adjust the patch accordingly.
Michael
On Mon, 2023-07-03 at 17:38 +0200, Andrew Lunn wrote:
> On Mon, Jul 03, 2023 at 05:26:06PM +0200, M. Haener wrote:
> > From: Michael Haener <michael.haener@siemens.com>
> >
> > This patch series brings SERDES support for the mv88e632x family.
>
> Please take a look at Russell Kings series:
>
> https://www.spinics.net/lists/netdev/msg914908.html
>
> It would be good if you could build on top of that, which we should
> be
> merging soon.
>
> Andrew
prev parent reply other threads:[~2023-07-04 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:26 M. Haener
2023-07-03 15:26 ` [PATCH 1/3] net: dsa: mv88e632x: Refactor serdes read M. Haener
2023-07-03 15:26 ` [PATCH 2/3] net: dsa: mv88e632x: Refactor serdes write M. Haener
2023-07-03 15:26 ` [PATCH 3/3] net: dsa: mv88e632x: Add SERDES ops M. Haener
2023-07-03 15:38 ` [PATCH 0/3] net: dsa: SERDES support for mv88e632x family Andrew Lunn
2023-07-04 6:11 ` Haener, Michael [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=3322f0995be4b49bcc349d7a58ec9114fca6c3f9.camel@siemens.com \
--to=michael.haener@siemens.com \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®