From: David Miller <davem@davemloft.net>
To: michael@walle.cc
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, andrew@lunn.ch, olteanv@gmail.com,
alexandru.marginean@nxp.com, claudiu.manoil@nxp.com,
heiko.thiery@gmail.com, linux@armlinux.org.uk,
ioana.ciornei@nxp.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v7 0/4] net: enetc: remove bootloader dependency
Date: Sun, 19 Jul 2020 18:06:05 -0700 (PDT) [thread overview]
Message-ID: <20200719.180605.1081706615520028720.davem@davemloft.net> (raw)
In-Reply-To: <20200719220336.6919-1-michael@walle.cc>
From: Michael Walle <michael@walle.cc>
Date: Mon, 20 Jul 2020 00:03:32 +0200
> These patches were picked from the following series:
> https://lore.kernel.org/netdev/1567779344-30965-1-git-send-email-claudiu.manoil@nxp.com/
> They have never been resent. I've picked them up, addressed Andrews
> comments, fixed some more bugs and asked Claudiu if I can keep their SOB
> tags; he agreed. I've tested this on our board which happens to have a
> bootloader which doesn't do the enetc setup in all cases. Though, only
> SGMII mode was tested.
...
Series applied, thank you.
prev parent reply other threads:[~2020-07-20 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 22:03 [PATCH net-next v7 0/4] net: enetc: remove bootloader dependency Michael Walle
2020-07-19 22:03 ` [PATCH net-next v7 1/4] net: phy: add USXGMII link partner ability constants Michael Walle
2020-07-19 22:03 ` [PATCH net-next v7 2/4] net: dsa: felix: (re)use already existing constants Michael Walle
2020-07-19 22:03 ` [PATCH net-next v7 3/4] net: enetc: Initialize SerDes for SGMII and USXGMII protocols Michael Walle
2020-07-19 22:03 ` [PATCH net-next v7 4/4] net: enetc: Use DT protocol information to set up the ports Michael Walle
2020-07-20 1:06 ` David Miller [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=20200719.180605.1081706615520028720.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandru.marginean@nxp.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=heiko.thiery@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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).