Linux Kernel Selftest development
 help / color / mirror / Atom feed
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 12:24:56 -0700	[thread overview]
Message-ID: <779d0e08-216a-45e9-991a-80a7ec23280d@nvidia.com> (raw)
In-Reply-To: <CAG4es9V4EiVBi08X7xNrEpCd5eUum1-5DrYV7+52BB=OP_4DKA@mail.gmail.com>

On 7/2/24 11:49 AM, Edward Liaw wrote:
> On Tue, Jul 2, 2024 at 11:26 AM John Hubbard <jhubbard@nvidia.com> wrote:
>>
>> 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.
> 
> I don't really know, but it was suggested to me that it can help to
> point out that the patch might have been missed before.
> 

I wish. But we are three versions into it, plus a special email [1]
specifically to point out that this is still pending.

I think either people are on vacation, or these fixes are not considered
sufficiently important, or both. :)


[1] https://lore.kernel.org/e9de90dd-c541-45bf-a364-0e7aaf320314@nvidia.com

thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2024-07-02 19: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
2024-07-02 18:49       ` Edward Liaw
2024-07-02 19:24         ` John Hubbard [this message]
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=779d0e08-216a-45e9-991a-80a7ec23280d@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