From: Vladimir Oltean <olteanv@gmail.com>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH] net: dsa: qca8k: make sure PAD0 MAC06 exchange is disabled
Date: Tue, 2 Nov 2021 20:38:40 +0200 [thread overview]
Message-ID: <20211102183840.44mmy5mklmuluct7@skbuf> (raw)
In-Reply-To: <YYGDYoToj2r/uYIE@Ansuel-xps.localdomain>
On Tue, Nov 02, 2021 at 07:28:50PM +0100, Ansuel Smith wrote:
> On Tue, Nov 02, 2021 at 08:26:55PM +0200, Vladimir Oltean wrote:
> > On Tue, Nov 02, 2021 at 06:56:29PM +0100, Ansuel Smith wrote:
> > > Some device set MAC06 exchange in the bootloader. This cause some
> > > problem as we don't support this strange mode and we just set the port6
> > > as the primary CPU port. With MAC06 exchange, PAD0 reg configure port6
> > > instead of port0. Add an extra check and explicitly disable MAC06 exchange
> > > to correctly configure the port PAD config.
> > >
> > > Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> > > ---
> >
> > Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
> >
> > Since net-next has closed, please add
> >
> > Fixes: 3fcf734aa482 ("net: dsa: qca8k: add support for cpu port 6")
> >
> > and resend to the "net" tree.
> >
>
> Oh sorry! I checked http://vger.kernel.org/~davem/net-next.html
> before posting and it does say it's open. Will resend sorry.
Closed or not, the point is that Jakub sent the "[GIT PULL] Networking for 5.16"
email today, so this code is no longer in net-next only.
prev parent reply other threads:[~2021-11-02 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 17:56 [net-next PATCH] net: dsa: qca8k: make sure PAD0 MAC06 exchange is disabled Ansuel Smith
2021-11-02 18:26 ` Vladimir Oltean
2021-11-02 18:28 ` Ansuel Smith
2021-11-02 18:38 ` Vladimir Oltean [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=20211102183840.44mmy5mklmuluct7@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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