[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHQZ30Dyj18+KQHZ9a5xAqDaGS4+gLAxQ9n8Liusn8eqE6pjFA@mail.gmail.com>
Date: Mon, 25 Nov 2019 11:12:53 -0700
From: Raul Rangel <rrangel@...omium.org>
To: Enric Balletbo i Serra <enric.balletbo@...labora.com>
Cc: Wolfram Sang <wsa@...-dreams.de>,
Akshu Agrawal <Akshu.Agrawal@....com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Guenter Roeck <groeck@...omium.org>,
Benson Leung <bleung@...omium.org>,
Neil Armstrong <narmstrong@...libre.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
"open list:I2C SUBSYSTEM HOST DRIVERS" <linux-i2c@...r.kernel.org>,
dlaurie@...omium.org
Subject: Re: [PATCH 2/4] i2c: i2c-cros-ec-tunnel: Fix ACPI identifier
On Mon, Nov 25, 2019 at 9:23 AM Enric Balletbo i Serra
<enric.balletbo@...labora.com> wrote:
>
> Hi Raul,
>
> On 21/11/19 22:10, Raul E Rangel wrote:
> > The initial patch was using the incorrect identifier.
> >
> > Signed-off-by: Raul E Rangel <rrangel@...omium.org>
> > ---
> > There are currently no boards using the identifier so it's fine to
> > change it.
> >
>
> Right, I don't see GOOG001A being used but also I don't see GOOG0012. Anyway,
> for the CrOS EC side, the change looks good to me. I think this will go through
> the I2C tree?
>
Is you were curious, here is the firmware patch:
https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/1928674
Powered by blists - more mailing lists