From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH] dsa: return error code upstream Date: Thu, 27 Dec 2018 17:53:18 -0800 (PST) Message-ID: <20181227.175318.1933639645603959141.davem@davemloft.net> References: <20181226040818.73764-1-kjlu@umn.edu> <20181227.162236.978596547594852209.davem@davemloft.net> <12500e65-ccc5-7545-4724-e328fa418576@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Cc: kjlu@umn.edu, pakki001@umn.edu, andrew@lunn.ch, vivien.didelot@gmail.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: f.fainelli@gmail.com Return-path: In-Reply-To: <12500e65-ccc5-7545-4724-e328fa418576@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Florian Fainelli Date: Thu, 27 Dec 2018 17:06:58 -0800 > Le 12/27/18 à 4:22 PM, David Miller a écrit : >> From: Kangjie Lu >> Date: Tue, 25 Dec 2018 22:08:18 -0600 >> >>> Both bcm_sf2_sw_indir_rw and mdiobus_write_nested could fail, so let's >>> return their error codes upstream. >>> >>> Signed-off-by: Kangjie Lu >> >> Applied with Subject line adjusted as per Florian's feedback. >> > > Thanks, technically bcm_sf2_sw_indir_rw() cannot fail and checking its > return value in the write (op == 0) case will always lead to returning 0 > anyway. In case this ever changes in the future, we should be more > future proof with that change anyway. Ok, thanks for the insight.