From: Andrew Lunn <andrew@lunn.ch>
To: Colin King <colin.king@canonical.com>
Cc: Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: dsa: bcm_sf2: remove redundant variable off
Date: Wed, 4 Jul 2018 16:25:20 +0200 [thread overview]
Message-ID: <20180704142520.GD12405@lunn.ch> (raw)
In-Reply-To: <20180704065436.13719-1-colin.king@canonical.com>
Hi Florian
I this a bug? It seems to be a result of moving to
b53_disable_port() in f86ad77faf.
Before you would handle the CPU port differently than a normal
port. After this change, there is no difference?
Andrew
next prev parent reply other threads:[~2018-07-04 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 6:54 [PATCH] net: dsa: bcm_sf2: remove redundant variable off Colin King
2018-07-04 13:40 ` David Miller
2018-07-04 14:25 ` Andrew Lunn [this message]
2018-07-04 19:55 ` Florian Fainelli
2018-07-09 16:10 ` Florian Fainelli
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=20180704142520.GD12405@lunn.ch \
--to=andrew@lunn.ch \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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