[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VCe+mf4fM79R2iunrvsS_A=G4Ha1z6M2z7J4Vq1e6=1A@mail.gmail.com>
Date: Tue, 17 Jun 2014 21:22:50 -0700
From: Doug Anderson <dianders@...omium.org>
To: Simon Glass <sjg@...omium.org>
Cc: Lee Jones <lee.jones@...aro.org>,
Andrew Bresticker <abrestic@...omium.org>,
Stephen Warren <swarren@...dotorg.org>,
Olof Johansson <olof@...om.net>,
Sonny Rao <sonnyrao@...omium.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Bill Richardson <wfrichar@...omium.org>,
Wolfram Sang <wsa@...-dreams.de>,
Mark Brown <broonie@...nel.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
lk <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 07/10] mfd: cros_ec: cleanup: remove unused fields from
struct cros_ec_device
Simon,
On Tue, Jun 17, 2014 at 8:39 PM, Simon Glass <sjg@...omium.org> wrote:
> Hi Doug,
>
> On 16 June 2014 14:39, Doug Anderson <dianders@...omium.org> wrote:
>> From: Bill Richardson <wfrichar@...omium.org>
>>
>> struct cros_ec_device has a superfluous "name" field. We can get all the
>> debugging info we need from the existing ec_name and phys_name fields, so
>> let's take out the extra field.
>
> Except that it no longer prints I2C/SPI - i.e. the transport that is
> used. Is that not considered important?
Before this change:
[ 1.895472] cros-ec-spi spi2.0: Chrome EC (SPI)
After this change:
[ 1.910671] cros-ec-spi spi2.0: Chrome EC device registered
I think having SPI in the name twice is probably enough. ;)
-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists