public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joseph, Jithu" <jithu.joseph@intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.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 13:10:04 -0800	[thread overview]
Message-ID: <2ab4c849-dfc2-4427-b6df-2f2c070e7933@intel.com> (raw)
In-Reply-To: <50ba78dc-f60d-63de-80fd-ef9b1fc68c72@linux.intel.com>



On 2/4/2025 12:07 AM, Ilpo Järvinen wrote:
> 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.

Thank you, Anisse,  for reporting this, and apologies for missing the Reported-by tag.

Thanks Ilpo for taking the patch and Tony for your inputs on how to go about this.

> 
> Thanks Anisse for raising this issue and Jithu for getting the gears 
> moving to provide an useful resolution.
> 

Jithu

  reply	other threads:[~2025-02-04 21:10 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
2025-02-04 21:10   ` Joseph, Jithu [this message]
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=2ab4c849-dfc2-4427-b6df-2f2c070e7933@intel.com \
    --to=jithu.joseph@intel.com \
    --cc=anisse@astier.eu \
    --cc=ashok.raj.linux@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox