From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754582AbdKAMhI (ORCPT ); Wed, 1 Nov 2017 08:37:08 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:36456 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754336AbdKAMhG (ORCPT ); Wed, 1 Nov 2017 08:37:06 -0400 Date: Wed, 1 Nov 2017 13:37:05 +0100 From: Andrew Lunn To: "Maciej S. Szmigiero" Cc: Florian Fainelli , netdev@vger.kernel.org, linux-kernel Subject: Re: [PATCH v2] net: phy: leds: Add support for "link" trigger Message-ID: <20171101123705.GG12680@lunn.ch> References: <52ce25a6-8d6b-039d-ca08-90595eb9ee72@maciej.szmigiero.name> <20171101121611.GD12680@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Maciej I don't particularly like the if (!phy->link) goto out_change_speed; part of the existing code. Makes me thing of BASIC. goto is good for error handling, but this is not an error. If you feel like it, maybe you can refactor this code? Add a function like: phy_led_trigger_no_link(struct phy_device *phy) { if (phy->last_triggered) { led_trigger_event(&phy->last_triggered->trigger, LED_OFF); phy->last_triggered = NULL; } } and call it, rather than using goto? It then becomes a lot more obvious what your change is doing, turning the LED off when there is no link. Thanks Andrew