From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jithu Joseph <jithu.joseph@intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org, tony.luck@intel.com,
ashok.raj.linux@gmail.com, anisse@astier.eu
Subject: Re: [PATCH] platform/x86/intel/ifs: Update documentation with image download path
Date: Tue, 4 Feb 2025 10:07:29 +0200 (EET) [thread overview]
Message-ID: <50ba78dc-f60d-63de-80fd-ef9b1fc68c72@linux.intel.com> (raw)
In-Reply-To: <20250131205315.1585663-1-jithu.joseph@intel.com>
On Fri, 31 Jan 2025, Jithu Joseph wrote:
> The documentation previously listed the path to download In Field Scan
> (IFS) test images as "TBD".
>
> Update the documentation to include the correct image download location.
> Also move the download link to the appropriate section within the doc.
>
> Signed-off-by: Jithu Joseph <jithu.joseph@intel.com>
I've applied this patch into the fixes branch with Anisse added as
Reported-by.
Thanks Anisse for raising this issue and Jithu for getting the gears
moving to provide an useful resolution.
> ---
> drivers/platform/x86/intel/ifs/ifs.h | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/ifs/ifs.h b/drivers/platform/x86/intel/ifs/ifs.h
> index 5c3c0dfa1bf8..41fc21e7ef14 100644
> --- a/drivers/platform/x86/intel/ifs/ifs.h
> +++ b/drivers/platform/x86/intel/ifs/ifs.h
> @@ -23,12 +23,14 @@
> * IFS Image
> * ---------
> *
> - * Intel provides a firmware file containing the scan tests via
> - * github [#f1]_. Similar to microcode there is a separate file for each
> + * Intel provides firmware files containing the scan tests via the webpage [#f1]_.
> + * Look under "In-Field Scan Test Images Download" section towards the
> + * end of the page. Similar to microcode there are separate files for each
> * family-model-stepping. IFS Images are not applicable for some test types.
> * Wherever applicable the sysfs directory would provide a "current_batch" file
> * (see below) for loading the image.
> *
> + * .. [#f1] https://intel.com/InFieldScan
> *
> * IFS Image Loading
> * -----------------
> @@ -125,9 +127,6 @@
> * 2) Hardware allows for some number of cores to be tested in parallel.
> * The driver does not make use of this, it only tests one core at a time.
> *
> - * .. [#f1] https://github.com/intel/TBD
> - *
> - *
> * Structural Based Functional Test at Field (SBAF):
> * -------------------------------------------------
> *
>
> base-commit: ffd294d346d185b70e28b1a28abe367bbfe53c04
>
--
i.
next prev parent reply other threads:[~2025-02-04 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 20:53 [PATCH] platform/x86/intel/ifs: Update documentation with image download path Jithu Joseph
2025-02-04 8:07 ` Ilpo Järvinen [this message]
2025-02-04 21:10 ` Joseph, Jithu
2025-02-05 5:50 ` Anisse Astier
2025-02-05 6:31 ` Joseph, Jithu
2025-02-05 6:37 ` Anisse Astier
2025-02-05 16:26 ` Luck, Tony
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=50ba78dc-f60d-63de-80fd-ef9b1fc68c72@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=anisse@astier.eu \
--cc=ashok.raj.linux@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.