From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v4 3/3] net: phy: leds: add support for led triggers on phy link state change Date: Thu, 13 Oct 2016 11:59:56 -0400 (EDT) Message-ID: <20161013.115956.2197317299874950600.davem@davemloft.net> References: <1476217580-21229-4-git-send-email-zach.brown@ni.com> <20161013.104634.2079376697690971907.davem@davemloft.net> <20161013154246.GA17387@zach-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20161013154246.GA17387@zach-desktop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" To: zach.brown@ni.com Cc: devel@driverdev.osuosl.org, florian.c.schilhabel@googlemail.com, f.fainelli@gmail.com, andrew@lunn.ch, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, rpurdie@rpsys.net, gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net, j.anaszewski@samsung.com, linux-leds@vger.kernel.org, mlindner@marvell.com List-Id: linux-leds@vger.kernel.org From: Zach Brown Date: Thu, 13 Oct 2016 10:42:46 -0500 > Do you have suggestions on how to better handle the choice of the array size > and the speeds? All of the speed values are simply the rate in bits per second. There is therefore no reason you can't just print the raw value and scale it to whatever is appropriate ("MB/s", "GB/s", etc.)