[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9fce8b1c-e277-2eeb-4b0d-e6b0e1851419@collabora.com>
Date: Fri, 12 Apr 2019 11:23:19 +0200
From: Enric Balletbo i Serra <enric.balletbo@...labora.com>
To: Brian Norris <briannorris@...omium.org>,
Douglas Anderson <dianders@...omium.org>
Cc: Benson Leung <bleung@...omium.org>,
Alexandru M Stan <amstan@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Simon Glass <sjg@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Mark Brown <broonie@...nel.org>,
Ryan Case <ryandcase@...omium.org>,
Randall Spangler <rspangler@...omium.org>,
Matthias Kaehlcke <mka@...omium.org>,
Heiko Stuebner <heiko@...ech.de>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] platform/chrome: cros_ec_spi: Transfer messages at
high priority
Hi,
On 12/4/19 3:27, Brian Norris wrote:
> On Wed, Apr 3, 2019 at 1:32 PM Douglas Anderson <dianders@...omium.org> wrote:
>> +static int cros_ec_xfer_high_pri(struct cros_ec_device *ec_dev,
>> + struct cros_ec_command *ec_msg,
>> + cros_ec_xfer_fn_t fn)
>> +{
>> + struct cros_ec_xfer_work_params params;
>> +
>> + INIT_WORK(¶ms.work, cros_ec_xfer_high_pri_work);
>
> Sorry for the late review, but this should have been
> INIT_WORK_ONSTACK(). Should it be a new patch, or is this in a
> non-rebasing tree yet?
>
No need to resend, I'll do the modification myself and push again.
Thanks,
Enric
> Otherwise, looks fine to me:
>
> Reviewed-by: Brian Norris <briannorris@...omium.org>
>
Powered by blists - more mailing lists