Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Shuah Khan <skhan@linuxfoundation.org>, Shuah Khan <shuah@kernel.org>
Cc: "linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: resctrl selftest patches
Date: Thu, 13 Apr 2023 08:53:47 -0700	[thread overview]
Message-ID: <753f0eae-527d-c909-2b6e-8c59b788d4e2@intel.com> (raw)
In-Reply-To: <168d8f63-3d42-96e4-e8b1-89f92fb8cf36@intel.com>

Hi Shuah,

On 4/10/2023 11:39 AM, Reinette Chatre wrote:
> On 4/10/2023 11:25 AM, Shuah Khan wrote:
>> 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 see. What are your expectations for resctrl patches to be considered
> ready for inclusion?
> 
>> I just applied them all.
>>
>> v9 patches are now in linux-kselftest next for Linux 6.4
>>
> 
> Thank you very much for picking up Ilpo's series.
> 
> Would you be ok to also pick up Shaopeng and Peter's contributions?
> 
> These are the following (nothing new, just copied from previous email):
> 
> [PATCH v8 0/6] Some improvements of resctrl selftest
> https://lore.kernel.org/lkml/20230215083230.3155897-1-tan.shaopeng@jp.fujitsu.com/

Shaopeng just sent a v9 with the only change being that it is rebased
on top of kselftest's next branch. This leaves you with no merge conflicts to
deal with:
https://lore.kernel.org/lkml/20230413072259.2089348-1-tan.shaopeng@jp.fujitsu.com/

Discussion surrounding this work completed a few months ago (it was ready before the
resctrl selftest series you merged this week and a couple of the patches also carry
your "Reviewed-by:"). I believe that it it ready for inclusion. Could you please
consider including this work in the kselftest repo?

> 
> [PATCH] selftests/resctrl: Use correct exit code when tests fail
> https://lore.kernel.org/lkml/20230309145757.2280518-1-peternewman@google.com/

This patch is also ready for inclusion and continues to apply cleanly.

Thank you very much

Reinette

  reply	other threads:[~2023-04-13 15:54 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
2023-04-10 18:39   ` Reinette Chatre
2023-04-13 15:53     ` Reinette Chatre [this message]
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=753f0eae-527d-c909-2b6e-8c59b788d4e2@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kselftest@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox