All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	Jinjie Ruan <ruanjinjie@huawei.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] entry: Split generic entry into generic exception and syscall entry
Date: Tue, 1 Jul 2025 11:28:30 +0100	[thread overview]
Message-ID: <aGO4Trd5qBJCrMH7@J2N7QTR9R3> (raw)
In-Reply-To: <87o6u5m7uh.ffs@tglx>

On Mon, Jun 30, 2025 at 07:56:22PM +0200, Thomas Gleixner wrote:
> On Tue, Jun 24 2025 at 20:35, Linus Walleij wrote:
> > From: Jinjie Ruan <ruanjinjie@huawei.com>
> >
> > Currently CONFIG_GENERIC_ENTRY enables both the generic exception
> > entry logic and the generic syscall entry logic, which are otherwise
> > loosely coupled.
> >
> > Introduce separate config options for these so that architectures can
> > select the two independently. This will make it easier for
> > architectures to migrate to generic entry code.
> >
> > Suggested-by: Mark Rutland <mark.rutland@arm.com>
> > Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> > Link: https://lore.kernel.org/20250213130007.1418890-2-ruanjinjie@huawei.com
> > [Linus Walleij: rebase onto v6.16-rc1]
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> 
> I merged this into tip based of v6.16-rc1 and tagged it so the commit
> can be pulled into arm[64] trees if needed.
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git entry-split-for-arm

Thanks, much appreciated!

Mark.

  reply	other threads:[~2025-07-01 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 18:35 [PATCH] entry: Split generic entry into generic exception and syscall entry Linus Walleij
2025-06-30 17:56 ` Thomas Gleixner
2025-07-01 10:28   ` Mark Rutland [this message]
2025-06-30 18:03 ` [tip: core/entry] " tip-bot2 for Jinjie Ruan

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=aGO4Trd5qBJCrMH7@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=ruanjinjie@huawei.com \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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 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.