public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joseph, Jithu" <jithu.joseph@intel.com>
To: Anisse Astier <anisse@astier.eu>
Cc: <platform-driver-x86@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Ashok Raj <ashok.raj.linux@gmail.com>,
	Tony Luck <tony.luck@intel.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	Ilpo J??rvinen <ilpo.jarvinen@linux.intel.com>,
	"Joseph, Jithu" <jithu.joseph@intel.com>
Subject: Re: [PATCH] platform/x86/intel/ifs: Update documentation to match current availability of firmware images
Date: Mon, 20 Jan 2025 12:47:13 -0800	[thread overview]
Message-ID: <58bc54d3-0abf-4d51-a592-465507f91bf8@intel.com> (raw)
In-Reply-To: <Z46vUgFJv6o-tNLq@kanto>



On 1/20/2025 12:20 PM, Anisse Astier wrote:
> Hi Jithu,
> 
> On Thu, Jan 02, 2025 at 01:40:23PM -0800, Joseph, Jithu wrote:
>>
>>
>> On 1/2/2025 11:43 AM, Anisse Astier wrote:
>>> I realize Intel had a few troubled years, and that having this feature
>>> in the kernel must be quite helpful to some users. But right now, it
>>> cannot be used unless one has a commercial relationship with Intel.
>>>
>>> I am not advocating for the removal of this driver; this is just an
>>> update of the documentation to show that the publication of the firmware
>>> images necessary to use the driver might have fallen through the cracks,
>>> and might not happen soon.
>>
>> Thanks for bringing this up ... apologies for the delay in making the images publicly available.
>> We have reached out to internal teams to speed this up.
>>
>> I will update the the documentation (or respond here) when I have more info
>>
>> In the meantime, I am okay with updating the documentation  to reflect the current state of image availability
>>
>>
>> Thanks
>> Jithu
> 
> Did you get any update?

Things have started moving internally towards this. I do anticipate at-least a few more weeks before having
a sharable link.

> 
> Do you think this doc patch could be queued for 6.14 or 6.15 ?

I don't have any objection in merging this doc patch with minor changes to commit message to indicate that only the 
scan test portion of the IFS test suite is affected by the lack of public image availability  ... 

I will comment on that in a separate reply



Thanks
Jithu

  reply	other threads:[~2025-01-20 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 19:43 [PATCH] platform/x86/intel/ifs: Update documentation to match current availability of firmware images Anisse Astier
2025-01-02 21:40 ` Joseph, Jithu
2025-01-20 20:20   ` Anisse Astier
2025-01-20 20:47     ` Joseph, Jithu [this message]
2025-01-20 20:59 ` Joseph, Jithu
2025-01-21 18:39   ` [PATCH v2] " Anisse Astier
2025-01-21 20:06     ` Joseph, Jithu
2025-01-22 13:42     ` Ilpo Järvinen
2025-01-31 21:00       ` Joseph, Jithu

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=58bc54d3-0abf-4d51-a592-465507f91bf8@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