From: Jeff Xu <jeffxu@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Liam.Howlett@oracle.com, agordeev@linux.ibm.com,
akpm@linux-foundation.org, borntraeger@linux.ibm.com,
edumazet@google.com, gor@linux.ibm.com,
guoweikang.kernel@gmail.com, hca@linux.ibm.com, kees@kernel.org,
kevin.brodsky@arm.com, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, m-malladi@ti.com,
svens@linux.ibm.com, thomas.weissschuh@linutronix.de,
zhengqi.arch@bytedance.com
Subject: Re: [PATCH v2 1/1] mseal sysmap: add arch-support txt
Date: Mon, 24 Mar 2025 07:53:14 -0700 [thread overview]
Message-ID: <CABi2SkUGLRb=WZMzDhY-8-hcTN_Rc4gxmGmksD2kQtqVcB8eRw@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWDrByGrgcTK9dRKRJyQ3ecQwadJjCcW=Nd0SjUeEukpg@mail.gmail.com>
Hi Geert
On Mon, Mar 24, 2025 at 2:03 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Jeff,
>
> On Fri, 21 Mar 2025 at 04:26, <jeffxu@chromium.org> wrote:
> > From: Jeff Xu <jeffxu@chromium.org>
> >
> > Add Documentation/features/core/mseal_sys_mappings/arch-support.txt
> >
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
>
> Thanks for your patch!
>
> > --- /dev/null
> > +++ b/Documentation/features/core/mseal_sys_mappings/arch-support.txt
> > @@ -0,0 +1,30 @@
> > +#
> > +# Feature name: mseal-system-mappings
> > +# Kconfig: ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS
> > +# description: arch supports mseal system mappings
> > +#
> > + -----------------------
> > + | arch |status|
> > + -----------------------
> > + | alpha: | TODO |
> > + | arc: | TODO |
>
> N/A (32-bit only)
>
> > + | arm: | N/A |
> > + | arm64: | ok |
> > + | csky: | TODO |
>
> N/A (32-bit only)
>
> > + | hexagon: | N/A |
> > + | loongarch: | TODO |
> > + | m68k: | TODO |
>
> N/A (32-bit only)
>
> > + | microblaze: | N/A |
> > + | mips: | TODO |
> > + | nios2: | TODO |
>
> N/A (32-bit only)
>
> > + | openrisc: | N/A |
> > + | parisc: | TODO |
> > + | powerpc: | TODO |
> > + | riscv: | TODO |
> > + | s390: | ok |
> > + | sh: | N/A |
> > + | sparc: | TODO |
> > + | um: | TODO |
> > + | x86: | ok |
> > + | xtensa: | TODO |
>
> N/A (32-bit only)
>
> > + -----------------------
> > --
> > 2.49.0.395.g12beb8f557-goog
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
Thanks for your expertise! I'll send V3 .
-Jeff
> 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
prev parent reply other threads:[~2025-03-24 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 3:26 [PATCH v2 0/1] " jeffxu
2025-03-21 3:26 ` [PATCH v2 1/1] " jeffxu
2025-03-24 9:03 ` Geert Uytterhoeven
2025-03-24 14:53 ` Jeff Xu [this message]
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='CABi2SkUGLRb=WZMzDhY-8-hcTN_Rc4gxmGmksD2kQtqVcB8eRw@mail.gmail.com' \
--to=jeffxu@chromium.org \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=gor@linux.ibm.com \
--cc=guoweikang.kernel@gmail.com \
--cc=hca@linux.ibm.com \
--cc=kees@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=m-malladi@ti.com \
--cc=svens@linux.ibm.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=zhengqi.arch@bytedance.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