From: Michael Walle <michael@walle.cc>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
Leo Li <leoyang.li@nxp.com>, Jakub Kicinski <kuba@kernel.org>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Ioana Ciornei <ioana.cionei@nxp.com>
Subject: Re: [PATCH net] arm64: dts: fsl-ls1028a-kontron-sl28: specify in-band mode for ENETC
Date: Mon, 09 Nov 2020 11:48:05 +0100 [thread overview]
Message-ID: <b73145462b236479629d6635533a6c0a@walle.cc> (raw)
In-Reply-To: <20201109104605.vzg2dt572krlijpk@skbuf>
Am 2020-11-09 11:46, schrieb Vladimir Oltean:
> On Sun, Nov 08, 2020 at 07:00:46PM +0100, Michael Walle wrote:
>> Hi,
>>
>> Am 2020-11-01 14:19, schrieb Michael Walle:
>> > Since commit 71b77a7a27a3 ("enetc: Migrate to PHYLINK and PCS_LYNX") the
>> > network port of the Kontron sl28 board is broken. After the migration to
>> > phylink the device tree has to specify the in-band-mode property. Add
>> > it.
>> >
>> > Fixes: 71b77a7a27a3 ("enetc: Migrate to PHYLINK and PCS_LYNX")
>> > Suggested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>> > Signed-off-by: Michael Walle <michael@walle.cc>
>>
>> Ping. will this go through the net queue or Shawn's queue. In any
>> case,
>> it should make it into a fixes queue, because this board is currently
>> broken in 5.10-rc2.
>
> Michael, this cannot go through the net queue, since you didn't copy
> netdev@vger.kernel.org to the email. It's not in Jakub's patchwork. My
> advice would be to resend it.
Oh damn. Thanks!
-michael
prev parent reply other threads:[~2020-11-09 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 13:19 [PATCH net] arm64: dts: fsl-ls1028a-kontron-sl28: specify in-band mode for ENETC Michael Walle
2020-11-01 13:43 ` Michael Walle
2020-11-01 16:32 ` Vladimir Oltean
2020-11-08 18:00 ` Michael Walle
2020-11-09 10:46 ` Vladimir Oltean
2020-11-09 10:48 ` Michael Walle [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=b73145462b236479629d6635533a6c0a@walle.cc \
--to=michael@walle.cc \
--cc=claudiu.manoil@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=ioana.cionei@nxp.com \
--cc=kuba@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=vladimir.oltean@nxp.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).