Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752201AbdGaODu (ORCPT ); Mon, 31 Jul 2017 10:03:50 -0400 Received: from mail.savoirfairelinux.com ([208.88.110.44]:57188 "EHLO mail.savoirfairelinux.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750987AbdGaODs (ORCPT ); Mon, 31 Jul 2017 10:03:48 -0400 From: Vivien Didelot To: Egil Hjelmeland , andrew@lunn.ch, f.fainelli@gmail.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@pengutronix.de Cc: Egil Hjelmeland Subject: Re: [PATCH net-next 2/2] net: dsa: lan9303: Simplify lan9303_xxx_packet_processing() usage In-Reply-To: <20170731113355.4284-3-privat@egil-hjelmeland.no> References: <20170731113355.4284-1-privat@egil-hjelmeland.no> <20170731113355.4284-3-privat@egil-hjelmeland.no> Date: Mon, 31 Jul 2017 10:00:53 -0400 Message-ID: <87379c4sfe.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2018 Lines: 73 Hi Egil, A few nitpicks below for lan9303_disable_processing. Egil Hjelmeland writes: > static int lan9303_disable_processing(struct lan9303 *chip) > { > - int ret; > + int p; > > - ret = lan9303_disable_packet_processing(chip, 0); > - if (ret) > - return ret; > - ret = lan9303_disable_packet_processing(chip, 1); > - if (ret) > - return ret; > - return lan9303_disable_packet_processing(chip, 2); > + for (p = 0; p <= 2; p++) { Exclusive limits are often prefer, i.e. 'p < 3'. > + int ret; > + > + ret = lan9303_disable_packet_processing(chip, p); > + if (ret) > + return ret; When any non-zero return code means an error, we usually see 'err' instead of 'ret'. > + } blank line before return statments are appreciated. > + return 0; > } > > static int lan9303_check_device(struct lan9303 *chip) > @@ -760,7 +761,6 @@ static int lan9303_port_enable(struct dsa_switch *ds, int port, > /* enable internal packet processing */ > switch (port) { > case 1: > - return lan9303_enable_packet_processing(chip, port); Is this deletion intentional? The commit message does not explain this. When possible, it is appreciated to separate functional from non-functional changes. For example one commit adding the loop in lan9303_disable_processing and another one to not enable/disable packet processing on port 1. > case 2: > return lan9303_enable_packet_processing(chip, port); > default: > @@ -779,13 +779,9 @@ static void lan9303_port_disable(struct dsa_switch *ds, int port, > /* disable internal packet processing */ > switch (port) { > case 1: > - lan9303_disable_packet_processing(chip, port); > - lan9303_phy_write(ds, chip->phy_addr_sel_strap + 1, > - MII_BMCR, BMCR_PDOWN); > - break; > case 2: > lan9303_disable_packet_processing(chip, port); > - lan9303_phy_write(ds, chip->phy_addr_sel_strap + 2, > + lan9303_phy_write(ds, chip->phy_addr_sel_strap + port, > MII_BMCR, BMCR_PDOWN); > break; Thanks, Vivien