linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: tklauser@distanz.ch, tklauser@distanz.ch
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu, rppt@kernel.org,
	Arnd Bergmann <arnd@arndb.de>,
	linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] riscv: Wire up memfd_secret in UAPI header
Date: Wed, 01 Jun 2022 22:57:21 -0700 (PDT)	[thread overview]
Message-ID: <mhng-671a8d6b-c318-431b-b209-c6bde465a420@palmer-ri-x1c9> (raw)
In-Reply-To: <20220505084611.tut66faep5r37r6c@distanz.ch>

On Thu, 05 May 2022 01:46:11 PDT (-0700), tklauser@distanz.ch wrote:
> On 2022-05-05 at 10:18:15 +0200, Tobias Klauser <tklauser@distanz.ch> wrote:
>> Move the __ARCH_WANT_MEMFD_SECRET define added in commit 7bb7f2ac24a0
>> ("arch, mm: wire up memfd_secret system call where relevant") to
>> <uapi/asm/unistd.h> so __NR_memfd_secret is defined when including
>> <unistd.h> in userspace.
>>
>> This allows the memds_secret selftest to pass on riscv.
>                   ^- this should say memfd_secret
>
> I can fix it up in a v2 if needed.

No big deal, I don't mind squashing stuff like that.  This is on 
for-next (no fixes, I'm still on 5.19).  I added

Fixes: 7bb7f2ac24a0 ("arch, mm: wire up memfd_secret system call where relevant")
Cc: stable@vger.kernel.org

but LMK if you think that's wrong for some reason.

Thanks!

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-06-02  5:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  8:18 [PATCH] riscv: Wire up memfd_secret in UAPI header Tobias Klauser
2022-05-05  8:46 ` Tobias Klauser
2022-06-02  5:57   ` Palmer Dabbelt [this message]
2022-06-02 13:03     ` Tobias Klauser

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=mhng-671a8d6b-c318-431b-b209-c6bde465a420@palmer-ri-x1c9 \
    --to=palmer@dabbelt.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.com \
    --cc=rppt@kernel.org \
    --cc=tklauser@distanz.ch \
    /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 NNTP newsgroup(s).