From: Greg KH <gregkh@linuxfoundation.org>
To: Jithu Joseph <jithu.joseph@intel.com>
Cc: hdegoede@redhat.com, markgross@kernel.org, ashok.raj@intel.com,
tony.luck@intel.com, ravi.v.shankar@intel.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH] platform/x86/intel/ifs: Allow non-default names for IFS image
Date: Fri, 8 Jul 2022 17:28:02 +0200 [thread overview]
Message-ID: <YshNAh6awfPFmxzU@kroah.com> (raw)
In-Reply-To: <20220708151938.986530-1-jithu.joseph@intel.com>
On Fri, Jul 08, 2022 at 08:19:38AM -0700, Jithu Joseph wrote:
> Existing implementation limits IFS image to be loaded only from
> a default file-name (ff-mm-ss.scan).
>
> Change the semantics of the "reload" file. Writing "1" keeps the legacy
> behavior to reload from the default "ff-mm-ss.scan" file, but now interpret
> other strings as a filename to be loaded from the /lib/firmware/intel/ifs
> directory.
>
> Situations where multiple image files are helpful:
> 1. Test contents are larger than the memory reserved for IFS by BIOS
> 2. Increased test coverage
> 3. Custom test files to debug certain specific issues in field
Ick, but now what namespace are you saying that path is in? If you need
debugging stuff, then put the api/interface in debugfs and use it there,
don't overload the existing sysfs api to do something different here.
> Fix the below items in adjacent code
> - Return error when ifs_image_sanity_check() fails in ifs_load_firmware()
> - Correct documentation "ifs.0"->"ifs"
That should all be a separate patch, you and Tony know better than this.
{sigh}
greg k-h
next prev parent reply other threads:[~2022-07-08 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 15:19 [PATCH] platform/x86/intel/ifs: Allow non-default names for IFS image Jithu Joseph
2022-07-08 15:28 ` Greg KH [this message]
2022-07-08 18:34 ` Joseph, Jithu
2022-07-10 10:15 ` Greg KH
2022-07-10 13:42 ` Hans de Goede
2022-07-10 13:53 ` Greg KH
2022-07-10 14:08 ` Hans de Goede
2022-07-10 16:04 ` Joseph, Jithu
2022-07-10 16:09 ` Hans de Goede
2022-07-10 18:25 ` [PATCH 0/2] Two fixes for IFS Tony Luck
2022-07-10 18:25 ` [PATCH 1/2] Documentation: Correct IFS reload documentation Tony Luck
2022-07-10 20:00 ` Greg KH
2022-07-10 18:25 ` [PATCH 2/2] platform/x86/intel/ifs: return error on load failure Tony Luck
2022-07-10 19:57 ` [PATCH 0/2] Two fixes for IFS Hans de Goede
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=YshNAh6awfPFmxzU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashok.raj@intel.com \
--cc=hdegoede@redhat.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=patches@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=tony.luck@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