public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	markgross@kernel.org,  Jithu Joseph <jithu.joseph@intel.com>,
	rostedt@goodmis.org,  tony.luck@intel.com,
	LKML <linux-kernel@vger.kernel.org>,
	 platform-driver-x86@vger.kernel.org, patches@lists.linux.dev,
	 pengfei.xu@intel.com
Subject: Re: [PATCH 0/5] Miscelleanous fixes and improvements to Infield Scan
Date: Wed, 31 Jan 2024 12:29:24 +0200 (EET)	[thread overview]
Message-ID: <8e9097cf-51f9-a151-bfa5-1580a4166607@linux.intel.com> (raw)
In-Reply-To: <20240125082254.424859-1-ashok.raj@intel.com>

On Thu, 25 Jan 2024, Ashok Raj wrote:

> Hi Hans,
> 
> This series has some bug fixes and improvements for Infield Scan.
> 
> Patch1 - fixes a bug in the driver that didn't release_firmware() in the
> 	 error path.
> 
> Patch2, 3 - Added some improved tracing.
> 
> Patch4 - Moves the rendezvous to function entry
> Patch5 - Adds entry rendezvous for IFS.
> 
> Cheers,
> Ashok
> 
> 
> Ashok Raj (4):
>   platform/x86/intel/ifs: Trace on all HT threads when executing a test
>   platform/x86/intel/ifs: Add current batch number to trace output
>   platform/x86/intel/ifs: Replace the exit rendezvous with an entry rendezvous for ARRAY_BIST
>   platform/x86/intel/ifs: Add an entry rendezvous for SAF

Patches 2-5 applied to review-ilpo.

-- 
 i.


      parent reply	other threads:[~2024-01-31 10:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  8:22 [PATCH 0/5] Miscelleanous fixes and improvements to Infield Scan Ashok Raj
2024-01-25  8:22 ` [PATCH 1/5] platform/x86/intel/ifs: Call release_firmware() when handling errors Ashok Raj
2024-01-25 13:04   ` Ilpo Järvinen
2024-01-26 19:15   ` Hans de Goede
2024-01-29  3:55     ` Pengfei Xu
2024-01-29  8:39       ` Hans de Goede
2024-01-25  8:22 ` [PATCH 2/5] platform/x86/intel/ifs: Trace on all HT threads when executing a test Ashok Raj
2024-01-25  8:22 ` [PATCH 3/5] platform/x86/intel/ifs: Add current batch number to trace output Ashok Raj
2024-01-25  8:22 ` [PATCH 4/5] platform/x86/intel/ifs: Replace the exit rendezvous with an entry rendezvous for ARRAY_BIST Ashok Raj
2024-01-25  8:22 ` [PATCH 5/5] platform/x86/intel/ifs: Add an entry rendezvous for SAF Ashok Raj
2024-01-31 10:29 ` Ilpo Järvinen [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=8e9097cf-51f9-a151-bfa5-1580a4166607@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --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=pengfei.xu@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rostedt@goodmis.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