All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joseph, Jithu" <jithu.joseph@intel.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Pengfei Xu <pengfei.xu@intel.com>, <shuah@kernel.org>,
	linux-kselftest <linux-kselftest@vger.kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	<ashok.raj@intel.com>, <sathyanarayanan.kuppuswamy@intel.com>
Subject: Re: [PATCH v1 0/4] add tests to verify IFS (In Field Scan) driver functionality
Date: Tue, 14 May 2024 10:39:22 -0700	[thread overview]
Message-ID: <bfbf8ec7-4deb-47a5-88ee-7d836ea13470@intel.com> (raw)
In-Reply-To: <58fd25ea-c444-45cf-a41d-c3022e9d5f80@linuxfoundation.org>

Hi Shuah,

On 5/14/2024 9:45 AM, Shuah Khan wrote:
> On 4/29/24 21:31, Pengfei Xu wrote:
>> To verify IFS (In Field Scan [1]) driver functionality, add the following 6
>> test cases:

...
>>
> 
> I am fine with adding a test. I would need ifs ack or reviewed-by.
> I don't see ifs maintainer on on this thread.

I am the IFS driver maintainer,  and I have reviewed the series and Pengfei has
my reviewed-by tags added in all the 4 patches.

Thanks
Jithu

  reply	other threads:[~2024-05-14 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  3:31 [PATCH v1 0/4] add tests to verify IFS (In Field Scan) driver functionality Pengfei Xu
2024-04-30  3:31 ` [PATCH v1 1/4] selftests: ifs: verify test interfaces are created by the driver Pengfei Xu
2024-04-30  3:31 ` [PATCH v1 2/4] selftests: ifs: verify test image loading functionality Pengfei Xu
2024-04-30  3:31 ` [PATCH v1 3/4] selftests: ifs: verify IFS scan test functionality Pengfei Xu
2024-04-30  3:31 ` [PATCH v1 4/4] selftests: ifs: verify IFS ARRAY BIST functionality Pengfei Xu
2024-05-14 16:45 ` [PATCH v1 0/4] add tests to verify IFS (In Field Scan) driver functionality Shuah Khan
2024-05-14 17:39   ` Joseph, Jithu [this message]
2024-05-15  3:55 ` Kuppuswamy, Sathyanarayanan
2024-05-15  5:15   ` Pengfei Xu

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=bfbf8ec7-4deb-47a5-88ee-7d836ea13470@intel.com \
    --to=jithu.joseph@intel.com \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pengfei.xu@intel.com \
    --cc=sathyanarayanan.kuppuswamy@intel.com \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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.