[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gmJYZ==O_xn7v+=-9dr9n+GvV2TmcjWVsRvXc4F2UcYQ@mail.gmail.com>
Date: Wed, 28 Feb 2024 22:14:36 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>, Sakari Ailus <sakari.ailus@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>, Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v2 2/4] driver core: Move fw_devlink stuff to where it belongs
On Fri, Feb 23, 2024 at 4:57 PM Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
>
> A few APIs that belong specifically to the fw_devlink APIs
It would be better to say which functions specifically you mean here.
> - are exposed to others without need
This is not particularly precise. I guess you mean that they could be
static and are not, which is fair enough, but why not just say that?
> - prevents device property code to be cleaned up in the future
This is completely unclear to me.
> Resolve this mess by moving fw_devlink code to where it belongs
> and hide from others.
This could be more precise.
Also I think that the patch is not expected to introduce functional
changes, which could be mentioned here.
Powered by blists - more mailing lists