From: Evan Green <evan@rivosinc.com>
To: libc-alpha@sourceware.org
Cc: vineetg@rivosinc.com, slewis@rivosinc.com, palmer@rivosinc.com,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v10 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface
Date: Mon, 8 Jan 2024 09:06:10 -0800 [thread overview]
Message-ID: <CALs-Hst5TZm75v8VKxdS1G1rXFhP9QtR8hBdJBSJN+X6AXdBqw@mail.gmail.com> (raw)
In-Reply-To: <20231213211142.1543025-1-evan@rivosinc.com>
Any last thoughts on this series? I think the plan is to land it shortly.
next prev parent reply other threads:[~2024-01-08 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 21:11 Evan Green
2023-12-13 21:11 ` [PATCH v10 1/7] riscv: Add Linux hwprobe syscall support Evan Green
2023-12-13 21:11 ` [PATCH v10 2/7] linux: Introduce INTERNAL_VSYSCALL Evan Green
2023-12-13 21:11 ` [PATCH v10 3/7] riscv: Add hwprobe vdso call support Evan Green
2023-12-13 21:11 ` [PATCH v10 4/7] riscv: Add __riscv_hwprobe pointer to ifunc calls Evan Green
2023-12-13 21:11 ` [PATCH v10 5/7] riscv: Enable multi-arg ifunc resolvers Evan Green
2023-12-13 21:11 ` [PATCH v10 6/7] riscv: Add ifunc helper method to hwprobe.h Evan Green
2024-01-08 18:53 ` Adhemerval Zanella Netto
2023-12-13 21:11 ` [PATCH v10 7/7] riscv: Add and use alignment-ignorant memcpy Evan Green
2024-01-08 18:56 ` Adhemerval Zanella Netto
2024-01-08 17:06 ` Evan Green [this message]
2024-01-08 18:10 ` [PATCH v10 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Palmer Dabbelt
2024-01-09 12:06 ` Stefan O'Rear
2024-01-09 17:10 ` Evan Green
2024-01-09 18:29 ` Stefan O'Rear
2024-01-09 18:41 ` Evan Green
2024-01-09 19:09 ` Stefan O'Rear
2024-01-09 19:18 ` enh
2024-01-09 19:36 ` Evan Green
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=CALs-Hst5TZm75v8VKxdS1G1rXFhP9QtR8hBdJBSJN+X6AXdBqw@mail.gmail.com \
--to=evan@rivosinc.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@rivosinc.com \
--cc=slewis@rivosinc.com \
--cc=vineetg@rivosinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).