mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jesung Yang <y.j3ms.n@gmail.com>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jesung Yang <y.j3ms.n@gmail.com>
Subject: Re: [PATCH] docs: align with scripts/syscall.tbl migration
Date: Tue, 06 May 2025 07:01:01 -0600	[thread overview]
Message-ID: <87v7qdx59u.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250504093351.2134552-1-y.j3ms.n@gmail.com>

Jesung Yang <y.j3ms.n@gmail.com> writes:

> Update the documentation to reflect the migration of the following
> architectures to the centralized syscall table format:
>
>   arc, arm64, csky, hexagon, loongarch, nios2, openrisc, riscv
>
> As of commit 3db80c999debbad ("riscv: convert to generic syscall table"),
> these architectures no longer rely on include/uapi/asm-generic/unistd.h.
> Instead, syscall table headers (syscall_table_{32,64}.h) are generated by
> scripts/syscalltbl.sh based on entries in scripts/syscall.tbl, with ABIs
> specified in arch/*/kernel/Makefile.syscalls.
>
> For the convenience of developers working with older kernel versions, the
> original documentation is fully retained, with new sections added to
> cover the scripts/syscall.tbl approach.
>
> Verified with `make htmldocs`.
>
> Signed-off-by: Jesung Yang <y.j3ms.n@gmail.com>
> Link: https://lore.kernel.org/lkml/20240704143611.2979589-1-arnd@kernel.org

So this seems fine to me, but I would feel a bit better about it if the
relevant architecture maintainers and lists had been copied.  Could I
convince you to repost with those addresses included?

Thanks,

jon

  reply	other threads:[~2025-05-06 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04  9:33 Jesung Yang
2025-05-06 13:01 ` Jonathan Corbet [this message]
2025-05-06 19:29   ` Jesung Yang
2025-05-06 19:48 Jesung Yang
2025-05-19 15:40 ` Jonathan Corbet

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=87v7qdx59u.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=workflows@vger.kernel.org \
    --cc=y.j3ms.n@gmail.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

all inboxes | Powered by JetHome®