From: John Hubbard <jhubbard@nvidia.com>
To: Edward Liaw <edliaw@google.com>
Cc: Shuah Khan <shuah@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Andy Lutomirski <luto@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, Carlos Llamas <cmllamas@google.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: [PATCH v3 1/3] selftests/vDSO: fix clang build errors and warnings
Date: Tue, 2 Jul 2024 11:25:01 -0700 [thread overview]
Message-ID: <b4720a40-6e74-4b1d-93ca-a3444e400a1a@nvidia.com> (raw)
In-Reply-To: <CAG4es9WQOOga8Oh9BOjr_JXy5gcUzVN0iTtfjN_HVdRj7_G7iQ@mail.gmail.com>
On 7/2/24 11:12 AM, Edward Liaw wrote:
> On Fri, Jun 14, 2024 at 4:31 PM John Hubbard <jhubbard@nvidia.com> wrote:
...
> Hi John,
> Could you try re-submitting this series with the RESEND prefix?
>
> Thanks,
> Edward
Sure. Is that the key, for kselftests? Because I've got 5+ small
patchsets that are languishing there, and I'm at a loss for how to even
get a response, much less get something merged.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2024-07-02 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 23:31 [PATCH v3 0/3] selftests/vDSO: fix clang build errors, and Makefile cleanup John Hubbard
2024-06-14 23:31 ` [PATCH v3 1/3] selftests/vDSO: fix clang build errors and warnings John Hubbard
2024-06-14 23:38 ` John Hubbard
2024-07-02 18:12 ` Edward Liaw
2024-07-02 18:25 ` John Hubbard [this message]
2024-07-02 18:49 ` Edward Liaw
2024-07-02 19:24 ` John Hubbard
2024-06-14 23:31 ` [PATCH v3 2/3] selftests/mm: remove partially duplicated "all:" target in Makefile John Hubbard
2024-06-14 23:31 ` [PATCH v3 3/3] selftests/vDSO: remove duplicate compiler invocations from Makefile John Hubbard
2024-06-14 23:34 ` [PATCH v3 0/3] selftests/vDSO: fix clang build errors, and Makefile cleanup John Hubbard
2024-06-17 20:15 ` Shuah, Andy L: " John Hubbard
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=b4720a40-6e74-4b1d-93ca-a3444e400a1a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=Jason@zx2c4.com \
--cc=broonie@kernel.org \
--cc=cmllamas@google.com \
--cc=colin.i.king@gmail.com \
--cc=edliaw@google.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
--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