All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>,
	Alexandre Ghiti <alexghiti@rivosinc.com>,
	Arnd Bergmann <arnd@arndb.de>, Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev
Subject: Re: [PATCH v6 0/4] entry: Move ret_from_fork() to C and inline syscall_exit_to_user_mode()
Date: Tue, 29 Apr 2025 08:22:44 +0200	[thread overview]
Message-ID: <87a57zqyff.ffs@tglx> (raw)
In-Reply-To: <aA_5IGGvXqB7v_EA@ghost>

On Mon, Apr 28 2025 at 14:54, Charlie Jenkins wrote:
> On Fri, Mar 21, 2025 at 10:22:36PM +0100, Thomas Gleixner wrote:
>> 
>> This looks sane now. I've bookmarked it as post-merge window material.
>
> Has this been applied somewhere?

Thanks for the nudge. It indeed fell through the cracks. Tending to it
now.

Thanks,

        tglx

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

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>,
	Alexandre Ghiti <alexghiti@rivosinc.com>,
	Arnd Bergmann <arnd@arndb.de>, Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev
Subject: Re: [PATCH v6 0/4] entry: Move ret_from_fork() to C and inline syscall_exit_to_user_mode()
Date: Tue, 29 Apr 2025 08:22:44 +0200	[thread overview]
Message-ID: <87a57zqyff.ffs@tglx> (raw)
In-Reply-To: <aA_5IGGvXqB7v_EA@ghost>

On Mon, Apr 28 2025 at 14:54, Charlie Jenkins wrote:
> On Fri, Mar 21, 2025 at 10:22:36PM +0100, Thomas Gleixner wrote:
>> 
>> This looks sane now. I've bookmarked it as post-merge window material.
>
> Has this been applied somewhere?

Thanks for the nudge. It indeed fell through the cracks. Tending to it
now.

Thanks,

        tglx

  reply	other threads:[~2025-04-29  6:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 17:29 [PATCH v6 0/4] entry: Move ret_from_fork() to C and inline syscall_exit_to_user_mode() Charlie Jenkins
2025-03-20 17:29 ` Charlie Jenkins
2025-03-20 17:29 ` [PATCH v6 1/4] riscv: entry: Convert ret_from_fork() to C Charlie Jenkins
2025-03-20 17:29   ` Charlie Jenkins
2025-04-29  6:33   ` [tip: core/entry] " tip-bot2 for Charlie Jenkins
2025-03-20 17:29 ` [PATCH v6 2/4] riscv: entry: Split ret_from_fork() into user and kernel Charlie Jenkins
2025-03-20 17:29   ` Charlie Jenkins
2025-03-21  6:36   ` Alexandre Ghiti
2025-03-21  6:36     ` Alexandre Ghiti
2025-04-29  6:33   ` [tip: core/entry] " tip-bot2 for Charlie Jenkins
2025-03-20 17:29 ` [PATCH v6 3/4] LoongArch: entry: Migrate ret_from_fork() to C Charlie Jenkins
2025-03-20 17:29   ` Charlie Jenkins
2025-04-29  6:33   ` [tip: core/entry] " tip-bot2 for Charlie Jenkins
2025-05-05  4:58   ` [PATCH v6 3/4] " Huacai Chen
2025-05-05  4:58     ` Huacai Chen
2025-03-20 17:29 ` [PATCH v6 4/4] entry: Inline syscall_exit_to_user_mode() Charlie Jenkins
2025-03-20 17:29   ` Charlie Jenkins
2025-04-29  6:33   ` [tip: core/entry] " tip-bot2 for Charlie Jenkins
2025-03-21 21:22 ` [PATCH v6 0/4] entry: Move ret_from_fork() to C and inline syscall_exit_to_user_mode() Thomas Gleixner
2025-03-21 21:22   ` Thomas Gleixner
2025-04-28 21:54   ` Charlie Jenkins
2025-04-28 21:54     ` Charlie Jenkins
2025-04-29  6:22     ` Thomas Gleixner [this message]
2025-04-29  6:22       ` Thomas Gleixner

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=87a57zqyff.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=alex@ghiti.fr \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=charlie@rivosinc.com \
    --cc=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=luto@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.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.