From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Saravana Kannan <saravanak@google.com>
Subject: Re: [PATCH v1 1/1] driver core: Move fw_devlink stuff to where it belongs
Date: Wed, 21 Feb 2024 14:49:54 +0200 [thread overview]
Message-ID: <ZdXxci3JXY-dV-eD@smile.fi.intel.com> (raw)
In-Reply-To: <ZdWqodFSRBZ1NAco@kekkonen.localdomain>
On Wed, Feb 21, 2024 at 07:47:45AM +0000, Sakari Ailus wrote:
> On Tue, Feb 20, 2024 at 06:10:02PM +0200, Andy Shevchenko wrote:
> > A few APIs that belong specifically to the fw_devlink APIs
> > - are exposed to others without need
> > - prevents device property code to be cleaned up in the future
> >
> > Resolve this mess by moving fw_devlink code to where it belongs
> > and hide from others.
> Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Thank you!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-02-21 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 16:10 [PATCH v1 1/1] driver core: Move fw_devlink stuff to where it belongs Andy Shevchenko
2024-02-21 2:08 ` Saravana Kannan
2024-02-21 12:48 ` Andy Shevchenko
2024-02-21 12:49 ` Andy Shevchenko
2024-02-23 0:54 ` Saravana Kannan
2024-02-23 14:53 ` Andy Shevchenko
2024-02-21 7:47 ` Sakari Ailus
2024-02-21 12:49 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZdXxci3JXY-dV-eD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=saravanak@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox