From: Reinette Chatre <reinette.chatre@intel.com>
To: Shuah Khan <skhan@linuxfoundation.org>, <fenghua.yu@intel.com>,
<shuah@kernel.org>, <tony.luck@intel.com>,
<peternewman@google.com>, <babu.moger@amd.com>,
<ilpo.jarvinen@linux.intel.com>
Cc: <maciej.wieczor-retman@intel.com>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 00/15] selftests/resctrl: Support diverse platforms with MBM and MBA tests
Date: Mon, 4 Nov 2024 16:55:21 -0800 [thread overview]
Message-ID: <bca5eea2-4088-4ba0-b313-66e15077b206@intel.com> (raw)
In-Reply-To: <c69d23f7-0c50-4f8a-b146-c76bc6f4291c@linuxfoundation.org>
On 11/4/24 4:07 PM, Shuah Khan wrote:
> On 11/4/24 16:14, Reinette Chatre wrote:
>>
>>
>> On 11/4/24 2:28 PM, Shuah Khan wrote:
>>> On 11/4/24 15:16, Reinette Chatre wrote:
>>>> Hi Shuah,
>>>>
>>>> On 10/24/24 3:36 PM, Shuah Khan wrote:
>>>>> On 10/24/24 15:18, Reinette Chatre wrote:
>>>>>
>>>>> Is this patch series ready to be applied?
>>>>>
>>>>
>>>> It is now ready after receiving anticipated tags. Could you please consider it for inclusion?
>>>>
>>>
>>> yes. I will apply the series for the next release.
>>>
>>
>> Thank you very much Shuah.
>>
>> Reinette
>
> Applied to linux-kselftest next for Linux 6.13-rc1.
>
> Tested on my system and worked fine.
Thank you very much Shuah. I received automated emails from patchwork-bot+linux-kselftest@kernel.org
indicating that versions 1, 2, and 3 were merged (no automated email about v4), but when looking
at the kselftest next branch it is clear that latest version, V4, was indeed merged and all looks good.
Thank you.
Reinette
prev parent reply other threads:[~2024-11-05 0:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 21:18 [PATCH V4 00/15] selftests/resctrl: Support diverse platforms with MBM and MBA tests Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 01/15] selftests/resctrl: Make functions only used in same file static Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 02/15] selftests/resctrl: Print accurate buffer size as part of MBM results Reinette Chatre
2024-10-25 13:52 ` Ilpo Järvinen
2024-10-24 21:18 ` [PATCH V4 03/15] selftests/resctrl: Fix memory overflow due to unhandled wraparound Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 04/15] selftests/resctrl: Protect against array overrun during iMC config parsing Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 05/15] selftests/resctrl: Protect against array overflow when reading strings Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 06/15] selftests/resctrl: Make wraparound handling obvious Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 07/15] selftests/resctrl: Remove "once" parameter required to be false Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 08/15] selftests/resctrl: Only support measured read operation Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 09/15] selftests/resctrl: Remove unused measurement code Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 10/15] selftests/resctrl: Make benchmark parameter passing robust Reinette Chatre
2024-10-25 13:52 ` Ilpo Järvinen
2024-10-24 21:18 ` [PATCH V4 11/15] selftests/resctrl: Ensure measurements skip initialization of default benchmark Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 12/15] selftests/resctrl: Use cache size to determine "fill_buf" buffer size Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 13/15] selftests/resctrl: Do not compare performance counters and resctrl at low bandwidth Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 14/15] selftests/resctrl: Keep results from first test run Reinette Chatre
2024-10-24 21:18 ` [PATCH V4 15/15] selftests/resctrl: Replace magic constants used as array size Reinette Chatre
2024-10-24 22:36 ` [PATCH V4 00/15] selftests/resctrl: Support diverse platforms with MBM and MBA tests Shuah Khan
2024-10-24 22:51 ` Reinette Chatre
2024-10-25 13:54 ` Ilpo Järvinen
2024-10-25 14:45 ` Reinette Chatre
2024-11-04 22:16 ` Reinette Chatre
2024-11-04 22:28 ` Shuah Khan
2024-11-04 23:14 ` Reinette Chatre
2024-11-05 0:07 ` Shuah Khan
2024-11-05 0:55 ` Reinette Chatre [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=bca5eea2-4088-4ba0-b313-66e15077b206@intel.com \
--to=reinette.chatre@intel.com \
--cc=babu.moger@amd.com \
--cc=fenghua.yu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=peternewman@google.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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