From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
alexander.usyskin@intel.com, tomas.winkler@intel.com,
Arnd Bergmann <arnd@arndb.de>,
wentong.wu@intel.com
Subject: Re: [PATCH 1/1] mei: vsc: Rework firmware image names
Date: Thu, 14 Dec 2023 18:00:54 +0200 [thread overview]
Message-ID: <ZXsmtrGerSc7MS8h@smile.fi.intel.com> (raw)
In-Reply-To: <20231213094055.446611-1-sakari.ailus@linux.intel.com>
On Wed, Dec 13, 2023 at 11:40:55AM +0200, Sakari Ailus wrote:
> Rework firmware image names with the users in mind---there's no need for
> variation between firmware names, apart from connected sensors. All
> supported SoCs use the same firmware, too.
>
> Use a single set of firmware binaries and assume they'll be found under
> intel/vsc directory.
I like it, FWIW,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-12-14 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 9:40 [PATCH 1/1] mei: vsc: Rework firmware image names Sakari Ailus
2023-12-14 16:00 ` 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=ZXsmtrGerSc7MS8h@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@intel.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