public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: guoren@kernel.org
Cc: arnd@arndb.de, linux-man@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
	Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH] set_thread_area.2: Add C-SKY document
Date: Sun, 15 Oct 2023 20:00:28 +0200	[thread overview]
Message-ID: <ZSwovaEr5JLrZA6z@debian> (raw)
In-Reply-To: <20231015150732.1991997-1-guoren@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

Hi Guo,

On Sun, Oct 15, 2023 at 11:07:32AM -0400, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
> 
> C-SKY only needs set_thread_area, no need for get_thread_area, the
> same as MIPS.
> 
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> ---

Patch applied.
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=1c4464ae2c40318b77e125961e24710d1784df5d>

Thanks!
Alex

>  man2/set_thread_area.2 | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/man2/set_thread_area.2 b/man2/set_thread_area.2
> index 02f65e0418f2..c43a92eb447a 100644
> --- a/man2/set_thread_area.2
> +++ b/man2/set_thread_area.2
> @@ -26,7 +26,7 @@ Standard C library
>  .B "int syscall(SYS_get_thread_area);"
>  .BI "int syscall(SYS_set_thread_area, unsigned long " tp );
>  .PP
> -.B #elif defined __mips__
> +.B #elif defined(__mips__ || defined __csky__)

I removed the parentheses here.

>  .PP
>  .BI "int syscall(SYS_set_thread_area, unsigned long " addr );
>  .PP
> @@ -42,17 +42,17 @@ These calls provide architecture-specific support for a thread-local storage
>  implementation.
>  At the moment,
>  .BR set_thread_area ()
> -is available on m68k, MIPS, and x86 (both 32-bit and 64-bit variants);
> +is available on m68k, MIPS, C-SKY, and x86 (both 32-bit and 64-bit variants);
>  .BR get_thread_area ()
>  is available on m68k and x86.
>  .PP
> -On m68k and MIPS,
> +On m68k, MIPS and C-SKY,
>  .BR set_thread_area ()
>  allows storing an arbitrary pointer (provided in the
>  .B tp
>  argument on m68k and in the
>  .B addr
> -argument on MIPS)
> +argument on MIPS and C-SKY)
>  in the kernel data structure associated with the calling thread;
>  this pointer can later be retrieved using
>  .BR get_thread_area ()
> @@ -139,7 +139,7 @@ return 0 on success, and \-1 on failure, with
>  .I errno
>  set to indicate the error.
>  .PP
> -On MIPS and m68k,
> +On C-SKY, MIPS and m68k,
>  .BR set_thread_area ()
>  always returns 0.
>  On m68k,
> -- 
> 2.36.1
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-10-15 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15 15:07 [PATCH] set_thread_area.2: Add C-SKY document guoren
2023-10-15 18:00 ` Alejandro Colomar [this message]
2023-10-16  0:53   ` Guo Ren

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=ZSwovaEr5JLrZA6z@debian \
    --to=alx@kernel.org \
    --cc=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox