Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Elizabeth Figura <zfigura@codeweavers.com>
To: shuah@kernel.org, Su Hui <suhui@nfschina.com>
Cc: Su Hui <suhui@nfschina.com>,
	wine-devel@winehq.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 3/4] selftests: ntsync: update config
Date: Fri, 14 Mar 2025 17:12:44 -0500	[thread overview]
Message-ID: <2267427.72vocr9iq0@camazotz> (raw)
In-Reply-To: <20250314071454.201697-4-suhui@nfschina.com>

On Friday, 14 March 2025 02:14:53 CDT Su Hui wrote:
> ntsync should be tested when CONFIG_NTSYNC is setting rather than
> CONFIG_WINESYNC, correct this.
> 
> Signed-off-by: Su Hui <suhui@nfschina.com>
> ---
>  tools/testing/selftests/drivers/ntsync/config | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/drivers/ntsync/config b/tools/testing/selftests/drivers/ntsync/config
> index 60539c826d06..0aa68de147af 100644
> --- a/tools/testing/selftests/drivers/ntsync/config
> +++ b/tools/testing/selftests/drivers/ntsync/config
> @@ -1 +1 @@
> -CONFIG_WINESYNC=y
> +CONFIG_NTSYNC=y
> 

Reviewed-by: Elizabeth Figura <zfigura@codeweavers.com>



      reply	other threads:[~2025-03-14 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  7:14 [PATCH 0/4] ntsync: some small fixes for doc and selftests Su Hui
2025-03-14  7:14 ` [PATCH 1/4] selftests: ntsync: fix the wrong condition in wake_all Su Hui
2025-03-14  9:21   ` Dan Carpenter
2025-03-14 22:12   ` Elizabeth Figura
2025-03-14  7:14 ` [PATCH 2/4] selftests: ntsync: avoid possible overflow in 32-bit machine Su Hui
2025-03-14 22:12   ` Elizabeth Figura
2025-03-14  7:14 ` [PATCH 3/4] selftests: ntsync: update config Su Hui
2025-03-14 22:12   ` Elizabeth Figura [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=2267427.72vocr9iq0@camazotz \
    --to=zfigura@codeweavers.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=suhui@nfschina.com \
    --cc=wine-devel@winehq.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