All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: leon.hwang@linux.dev
Cc: linux-mm@kvack.org, corbet@lwn.net, skhan@linuxfoundation.org,
	akpm@linux-foundation.org, liam@infradead.org, ljs@kernel.org,
	vbabka@kernel.org, jannh@google.com, pfalcato@suse.de,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, nathan@kernel.org, peterz@infradead.org,
	ojeda@kernel.org, nsc@kernel.org, tglx@kernel.org,
	thomas.weissschuh@linutronix.de, aliceryhl@google.com,
	dianders@chromium.org, gary@garyguo.net, linux.amoon@gmail.com,
	rdunlap@infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH] mm/mseal: fix mseal documentation for 32-bit kernels
Date: Fri,  3 Jul 2026 17:30:32 +0800	[thread overview]
Message-ID: <20260703093032.51640-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260703022507.187457-1-leon.hwang@linux.dev>


On Fri, Jul 03, 2026 at 10:25:07AM +0800, Leon Hwang wrote:
>mseal.o is built only for 64-bit kernels, so 32-bit kernels fall back
>to sys_ni_syscall() and return -ENOSYS rather than -EPERM.
>
>Document the -EINTR return from mmap_write_lock_killable(), fix the
>CONFIG_MSEAL_SYSTEM_MAPPINGS typo, and describe system mappings in
>terms of VM_SEALED_SYSMAP.
>
>Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>---

Thanks, free free to add:

Acked-by: Lance Yang <lance.yang@linux.dev>

WARNING: multiple messages have this Message-ID (diff)
From: Lance Yang <lance.yang@linux.dev>
To: leon.hwang@linux.dev
Cc: linux-doc@vger.kernel.org, peterz@infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	gary@garyguo.net, linux-riscv@lists.infradead.org,
	vbabka@kernel.org, thomas.weissschuh@linutronix.de,
	corbet@lwn.net, aliceryhl@google.com, ojeda@kernel.org,
	aou@eecs.berkeley.edu, jannh@google.com, nathan@kernel.org,
	skhan@linuxfoundation.org, pfalcato@suse.de, ljs@kernel.org,
	akpm@linux-foundation.org, alex@ghiti.fr, liam@infradead.org,
	nsc@kernel.org, rdunlap@infradead.org, dianders@chromium.org,
	Lance Yang <lance.yang@linux.dev>,
	palmer@dabbelt.com, tglx@kernel.org, pjw@kernel.org
Subject: Re: [PATCH] mm/mseal: fix mseal documentation for 32-bit kernels
Date: Fri,  3 Jul 2026 17:30:32 +0800	[thread overview]
Message-ID: <20260703093032.51640-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260703022507.187457-1-leon.hwang@linux.dev>


On Fri, Jul 03, 2026 at 10:25:07AM +0800, Leon Hwang wrote:
>mseal.o is built only for 64-bit kernels, so 32-bit kernels fall back
>to sys_ni_syscall() and return -ENOSYS rather than -EPERM.
>
>Document the -EINTR return from mmap_write_lock_killable(), fix the
>CONFIG_MSEAL_SYSTEM_MAPPINGS typo, and describe system mappings in
>terms of VM_SEALED_SYSMAP.
>
>Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>---

Thanks, free free to add:

Acked-by: Lance Yang <lance.yang@linux.dev>

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

  reply	other threads:[~2026-07-03  9:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  2:25 [PATCH] mm/mseal: fix mseal documentation for 32-bit kernels Leon Hwang
2026-07-03  2:25 ` Leon Hwang
2026-07-03  9:30 ` Lance Yang [this message]
2026-07-03  9:30   ` Lance Yang
2026-07-03  9:44 ` Thomas Weißschuh
2026-07-03  9:44   ` Thomas Weißschuh
2026-07-03 15:09   ` Leon Hwang
2026-07-03 15:09     ` Leon Hwang
2026-07-07 10:34     ` Thomas Weißschuh
2026-07-07 10:34       ` Thomas Weißschuh
2026-07-03  9:44 ` Pedro Falcato
2026-07-03  9:44   ` Pedro Falcato
2026-07-03 14:50   ` Leon Hwang
2026-07-03 14:50     ` Leon Hwang
2026-07-07 10:01     ` Pedro Falcato
2026-07-07 10:01       ` Pedro Falcato
2026-07-04  0:39 ` Matthew Wilcox
2026-07-04  0:39   ` Matthew Wilcox
2026-07-06  1:42   ` Leon Hwang
2026-07-06  1:42     ` Leon Hwang

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=20260703093032.51640-1-lance.yang@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aliceryhl@google.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=corbet@lwn.net \
    --cc=dianders@chromium.org \
    --cc=gary@garyguo.net \
    --cc=jannh@google.com \
    --cc=leon.hwang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux.amoon@gmail.com \
    --cc=ljs@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=pfalcato@suse.de \
    --cc=pjw@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=vbabka@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.