[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zl6GIDy_QT5iB8OS@google.com>
Date: Tue, 4 Jun 2024 03:12:32 +0000
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: Daisuke Nojiri <dnojiri@...omium.org>
Cc: Benson Leung <bleung@...omium.org>, Guenter Roeck <groeck@...omium.org>,
Hans Verkuil <hverkuil-cisco@...all.nl>,
Reka Norman <rekanorman@...omium.org>,
Abhishek Pandit-Subedi <abhishekpandit@...gle.com>,
Gwendal Grignou <gwendal@...omium.org>,
Pavan Holla <pholla@...omium.org>,
Ching-Kang Yen <chingkang@...omium.org>,
Lukasz Majczak <lma@...omium.org>,
Stephen Boyd <swboyd@...omium.org>,
Prashant Malani <pmalani@...omium.org>,
chrome-platform@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] platform/chrome: cros_ec_proto: Upgrade
get_next_event to v3
On Mon, Jun 03, 2024 at 05:53:12PM -0700, Daisuke Nojiri wrote:
> This CL upgrades get_next_event to version 3.
s/This CL upgrades/Upgrade/.
> BUG=b:331761304
> TEST=Type keys on Kyogre.
Please remove the tags as upstream doesn't use them.
> .../linux/platform_data/cros_ec_commands.h | 34 +++++++++++++++++++
Please separate the changes of the header into an independent patch. Says,
the changes in the header is a "sync" from include/ec_commands.h of EC which
is unlikely to be reverted. However, the rest of changes in the patch could
be reverted if something went wrong.
Powered by blists - more mailing lists