Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Reinette Chatre <reinette.chatre@intel.com>,
	Shuah Khan <shuah@kernel.org>
Cc: "linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: resctrl selftest patches
Date: Mon, 10 Apr 2023 12:25:10 -0600	[thread overview]
Message-ID: <71b769fd-6cde-0ccc-ca41-c94d4737b596@linuxfoundation.org> (raw)
In-Reply-To: <eaf96617-2f3e-b573-8990-6e9e6b0cb6fd@intel.com>

On 4/10/23 10:43, Reinette Chatre wrote:
> Hi Shuah and kselftest team,
> 
> There are a couple of resctrl selftest patches that are ready for inclusion. They have been percolating on the list for a while without expecting more feedback. All have "Reviewed-by" tags from at least one reviewer. Could you please consider including them into the kselftest repo? There is one minor merge conflict between two of the series for which the snippet below shows resolution.
> 
> [PATCH v8 0/6] Some improvements of resctrl selftest
> https://lore.kernel.org/lkml/20230215083230.3155897-1-tan.shaopeng@jp.fujitsu.com/
> 
> [PATCH v2 0/9] selftests/resctrl: Fixes to error handling logic and cleanups
> https://lore.kernel.org/lkml/20230215130605.31583-1-ilpo.jarvinen@linux.intel.com/
> 

I was waiting for another ack from x86, don't see one.
I just applied them all.

v9 patches are now in linux-kselftest next for Linux 6.4

thanks,
-- Shuah



  reply	other threads:[~2023-04-10 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 16:43 resctrl selftest patches Reinette Chatre
2023-04-10 18:25 ` Shuah Khan [this message]
2023-04-10 18:39   ` Reinette Chatre
2023-04-13 15:53     ` Reinette Chatre
2023-04-13 17:36       ` Shuah Khan
2023-04-13 17:40         ` Reinette Chatre

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=71b769fd-6cde-0ccc-ca41-c94d4737b596@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox