From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
tglx@linutronix.de
Subject: Re: [PATCH v15 3/5] arch: allocate vgetrandom_alloc() syscall number
Date: Wed, 22 May 2024 17:36:15 +0200 [thread overview]
Message-ID: <CAMuHMdUwVuVfAwDJkMNZFj+_+dKHFf1MX1=wrchUhHfKoP0Z6w@mail.gmail.com> (raw)
In-Reply-To: <20240521111958.2384173-4-Jason@zx2c4.com>
On Tue, May 21, 2024 at 1:21 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Add vgetrandom_alloc() as syscall 462 (or 572 on alpha) by adding it to
> all of the various syscall.tbl and unistd.h files.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> arch/m68k/kernel/syscalls/syscall.tbl | 1 +
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-05-22 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 11:18 [PATCH v15 0/5] implement getrandom() in vDSO Jason A. Donenfeld
2024-05-21 11:18 ` [PATCH v15 1/5] mm: add VM_DROPPABLE for designating always lazily freeable mappings Jason A. Donenfeld
2024-05-27 13:34 ` David Hildenbrand
2024-05-28 11:58 ` Jason A. Donenfeld
2024-05-21 11:18 ` [PATCH v15 2/5] random: add vgetrandom_alloc() syscall Jason A. Donenfeld
2024-05-21 11:48 ` Florian Weimer
2024-05-21 12:32 ` Jason A. Donenfeld
2024-05-21 11:18 ` [PATCH v15 3/5] arch: allocate vgetrandom_alloc() syscall number Jason A. Donenfeld
2024-05-22 15:36 ` Geert Uytterhoeven [this message]
2024-05-21 11:18 ` [PATCH v15 4/5] random: introduce generic vDSO getrandom() implementation Jason A. Donenfeld
2024-05-21 11:18 ` [PATCH v15 5/5] x86: vdso: Wire up getrandom() vDSO implementation Jason A. Donenfeld
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='CAMuHMdUwVuVfAwDJkMNZFj+_+dKHFf1MX1=wrchUhHfKoP0Z6w@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=tglx@linutronix.de \
/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).