[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yl307fUo09z2/M+w@chromium.org>
Date: Mon, 18 Apr 2022 23:31:57 +0000
From: Prashant Malani <pmalani@...omium.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Benson Leung <bleung@...omium.org>, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev, Lee Jones <lee.jones@...aro.org>,
Daisuke Nojiri <dnojiri@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
chrome-platform@...ts.linux.dev
Subject: Re: [PATCH 1/3] platform/chrome: cros_ec_proto: Add peripheral
charger count API
On Apr 18 16:29, Stephen Boyd wrote:
> Quoting Prashant Malani (2022-04-18 16:21:52)
> > On Apr 18 16:16, Stephen Boyd wrote:
> > >
> > > Sure. I take it that I can drop this function entirely then?
> >
> > Yeah, if it's a simple response, should be fine.
> >
> > > BTW, why is
> > > that function name the same as a struct name? It confuses my ctags.
> >
> > Yeahhh, didn't think about ctags... :/
> > Topic for another series: probably can be renamed to cros_ec_cmd() (just to keep ctags happy) ?
> >
>
> But then there'll be two cros_ec_cmd() because there's a
> cros-ec-regulator. Fun! :)
Ugh :S
I think we can get rid of that one; it looks to be the same as this
one :)
I'll write up a cleanup series if it all looks OK.
Powered by blists - more mailing lists