From: Shuah Khan <skhan@linuxfoundation.org>
To: paulmck@kernel.org, Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Willy Tarreau <w@1wt.eu>,
Shuah Khan <shuah@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 1/3] tools/nolibc/stdio: Implement vprintf()
Date: Tue, 11 Apr 2023 12:54:29 -0600 [thread overview]
Message-ID: <e81d0c3b-f301-e2cf-077d-fe9a934e7590@linuxfoundation.org> (raw)
In-Reply-To: <6a323775-6274-4d0c-844a-da53146c2abe@paulmck-laptop>
On 4/11/23 10:44, Paul E. McKenney wrote:
> On Tue, Apr 11, 2023 at 04:13:11PM +0100, Mark Brown wrote:
>> On Tue, Apr 11, 2023 at 04:03:21PM +0100, Will Deacon wrote:
>>> On Tue, Apr 11, 2023 at 03:31:10PM +0100, Mark Brown wrote:
>>
>>>> It seems like more of a kselftest change than anything else so probably
>>>> makes sense for it to go that way? The example user isn't really even
>>>> needed.
>>
>>> Fine by me, as long as it doesn't conflict with any other arm64 selftest
>>> changes you hope to land for 6.4.
>>
>> That shouldn't be an issue.
>
> Shuah, looks to me like this one is yours in kselftest, then. ;-)
>
> Thanx, Paul
I will pick these up for Linux 6.4
thanks,
-- Shuah
next prev parent reply other threads:[~2023-04-11 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 16:19 [PATCH v2 0/3] tools/nolibc: Support vprintf() so we can use kselftest.h with nolibc Mark Brown
2023-04-06 16:19 ` [PATCH v2 1/3] tools/nolibc/stdio: Implement vprintf() Mark Brown
2023-04-06 18:26 ` Willy Tarreau
2023-04-06 18:43 ` Paul E. McKenney
2023-04-10 18:30 ` Shuah Khan
2023-04-11 14:31 ` Mark Brown
2023-04-11 15:03 ` Will Deacon
2023-04-11 15:13 ` Mark Brown
2023-04-11 16:44 ` Paul E. McKenney
2023-04-11 18:54 ` Shuah Khan [this message]
2023-04-11 21:06 ` Will Deacon
2023-04-06 16:19 ` [PATCH v2 2/3] kselftest: Support nolibc Mark Brown
2023-04-06 16:19 ` [PATCH v2 3/3] kselftest/arm64: Convert za-fork to use kselftest.h Mark Brown
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=e81d0c3b-f301-e2cf-077d-fe9a934e7590@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
--cc=will@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