Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Shuah Khan <shuah@kernel.org>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andy Lutomirski <luto@mit.edu>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Mark Brown <broonie@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/5] selftests: vdso: Fix vDSO name for powerpc
Date: Fri, 30 Aug 2024 14:41:50 +0200	[thread overview]
Message-ID: <ZtG-DqWo8kBMocVh@zx2c4.com> (raw)
In-Reply-To: <6c5da802e72befecfa09046c489aa45d934d611f.1725020674.git.christophe.leroy@csgroup.eu>

Hi Shuah,

No 0/5 patch, so replying to the first one.

These are fixes to the vDSO selftests that Christophe is ostensibly
providing as a preamble to his work porting vgetrandom to PPC. Do you
mind if I take these via my random tree so his PPC vgetrandom code can
go on top of it?

Jason

  parent reply	other threads:[~2024-08-30 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 12:28 [PATCH 1/5] selftests: vdso: Fix vDSO name for powerpc Christophe Leroy
2024-08-30 12:28 ` [PATCH 2/5] selftests: vdso: Fix vdso_config " Christophe Leroy
2024-08-30 12:28 ` [PATCH 3/5] selftests: vdso: Fix vDSO symbols lookup for powerpc64 Christophe Leroy
2024-08-30 12:28 ` [PATCH 4/5] selftests: vdso: Fix the way vDSO functions are called for powerpc Christophe Leroy
2024-08-30 12:28 ` [PATCH 5/5] selftests: vdso: Use parse_vdso.h in vdso_test_abi Christophe Leroy
2024-08-30 12:41 ` Jason A. Donenfeld [this message]
2024-08-30 13:34   ` [PATCH 1/5] selftests: vdso: Fix vDSO name for powerpc Shuah Khan

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=ZtG-DqWo8kBMocVh@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=broonie@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luto@mit.edu \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@arm.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