From: John Hubbard <jhubbard@nvidia.com>
To: Carlos Llamas <cmllamas@google.com>
Cc: Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
Colin Ian King <colin.i.king@gmail.com>,
Valentin Obst <kernel@valentinobst.de>,
<linux-kselftest@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, <llvm@lists.linux.dev>
Subject: Re: [PATCH v2] selftests/vDSO: fix clang build errors and warnings
Date: Fri, 14 Jun 2024 15:56:01 -0700 [thread overview]
Message-ID: <8a6f384f-02b7-4a0b-90dd-e6843909e8a9@nvidia.com> (raw)
In-Reply-To: <2461f002-fdd4-4bf5-b797-827069cafc4b@nvidia.com>
On 6/14/24 3:51 PM, John Hubbard wrote:
> On 6/11/24 11:30 AM, Carlos Llamas wrote:
>> On Mon, May 27, 2024 at 02:16:22PM -0700, John Hubbard wrote:
...
>> Reviewed-by: Carlos Llamas <cmllamas@google.com>
>
> Thanks for the review! I have no earthly idea what will happen next.
> I'd like to hear at least something from the maintainers about their
> intentions here.
>
In fact, I have two more patches for vDSO (these are separate issues,
for the Makefile), and I just noticed that there are several accumulated
Reviewed-by and Tested-by tags on this patch here. So I think the way
forward is this:
I'll post a v3, with three patches for vDSO selftests, and the latest
tags. And let's see how that fares.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2024-06-14 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 21:16 [PATCH v2] selftests/vDSO: fix clang build errors and warnings John Hubbard
2024-05-29 8:05 ` Muhammad Usama Anjum
2024-05-30 19:24 ` John Hubbard
2024-06-04 21:18 ` [v2] " Edward Liaw
2024-06-11 18:30 ` [PATCH v2] " Carlos Llamas
2024-06-14 22:51 ` John Hubbard
2024-06-14 22:56 ` John Hubbard [this message]
2024-06-14 23:10 ` Carlos Llamas
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=8a6f384f-02b7-4a0b-90dd-e6843909e8a9@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=broonie@kernel.org \
--cc=cmllamas@google.com \
--cc=colin.i.king@gmail.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=shuah@kernel.org \
--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