public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Huang Rui <ray.huang@amd.com>,
	Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Shuah Khan <shuah@kernel.org>,
	"Meng, Li (Jassmine)" <Li.Meng@amd.com>,
	Doug Smythies <dsmythies@telus.net>,
	"kernel@collabora.com" <kernel@collabora.com>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: amd-pstate: fix TEST_FILES
Date: Fri, 3 Mar 2023 13:29:15 -0700	[thread overview]
Message-ID: <3d051308-382f-0f90-41b3-e1ffdd6f11f7@linuxfoundation.org> (raw)
In-Reply-To: <ZAGOQznWjSNuhn73@amd.com>

On 3/2/23 23:05, Huang Rui wrote:
> On Sat, Feb 04, 2023 at 09:34:54PM +0800, Guillaume Tucker wrote:
>> Bring back the Python scripts that were initially added with
>> TEST_GEN_FILES but now with TEST_FILES to avoid having them deleted
>> when doing a clean.  Also fix the way the architecture is being
>> determined as they should also be installed when ARCH=x86_64 is
>> provided explicitly.  Then also append extra files to TEST_FILES and
>> TEST_PROGS with += so they don't get discarded.
>>
>> Fixes: ba2d788aa873 ("selftests: amd-pstate: Trigger tbench benchmark and test cpus")
>> Fixes: ac527cee87c9 ("selftests: amd-pstate: Don't delete source files via Makefile")
>> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> 
> Acked-by: Huang Rui <ray.huang@amd.com>
> 

Thank you both. I will pick this up for 6.3-rc2

thanks,
-- Shuah


  reply	other threads:[~2023-03-03 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 13:34 [PATCH] selftests: amd-pstate: fix TEST_FILES Guillaume Tucker
2023-03-02 16:32 ` Guillaume Tucker
2023-03-03  6:05 ` Huang Rui
2023-03-03 20:29   ` Shuah Khan [this message]
2023-03-06 13:11     ` Guillaume Tucker

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=3d051308-382f-0f90-41b3-e1ffdd6f11f7@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=Li.Meng@amd.com \
    --cc=dsmythies@telus.net \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernel@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=ray.huang@amd.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