Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Xi Ruoyao <xry111@xry111.site>, Fangrui Song <i@maskray.me>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests/vDSO: support DT_GNU_HASH
Date: Tue, 3 Dec 2024 17:04:59 -0700	[thread overview]
Message-ID: <b2723ccd-bf0a-4d9b-a545-f9e3dc336539@linuxfoundation.org> (raw)
In-Reply-To: <c828b254fb93bd136b36d3a06ab1d9d29ce13d88.camel@xry111.site>

On 11/27/24 04:44, Xi Ruoyao wrote:
> On Thu, 2024-09-19 at 09:37 -0600, Shuah Khan wrote:
>> On 9/15/24 00:49, Fangrui Song wrote:
>>> glibc added support for DT_GNU_HASH in 2006 and DT_HASH has been
>>> obsoleted for more than one decade in many Linux distributions.
>>>
>>> Many vDSOs support DT_GNU_HASH. This patch adds selftests support.
>>>
>>> Signed-off-by: Fangrui Song <maskray@google.com>
>>> Tested-by: Xi Ruoyao <xry111@xry111.site>
>>> --
>>> Changes from v1:
>>> * fix style of a multi-line comment. ignore false positive suggestions from checkpath.pl: `ELF(Word) *`
>>> ---
>>>    tools/testing/selftests/vDSO/parse_vdso.c | 105 ++++++++++++++++------
>>>    1 file changed, 79 insertions(+), 26 deletions(-)
>>>
>>
>> Quick note that this will be picked up after the merge window closes.
> 
> Hi Shuah,
> 
> The patch seems forgotten.
> 

Thank for the reminder. I will pick this up now.

thanks,
-- Shuah

  reply	other threads:[~2024-12-04  0:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-15  6:49 [PATCH v2] selftests/vDSO: support DT_GNU_HASH Fangrui Song
2024-09-19 15:37 ` Shuah Khan
2024-11-27 11:44   ` Xi Ruoyao
2024-12-04  0:04     ` Shuah Khan [this message]
2024-12-04 22:30       ` Shuah Khan
2024-12-06 13:07         ` [PATCH v3] " Xi Ruoyao
2024-12-09 23:26           ` Shuah

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=b2723ccd-bf0a-4d9b-a545-f9e3dc336539@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=i@maskray.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=xry111@xry111.site \
    /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