From: Michael Ellerman <mpe@ellerman•id.au>
To: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Cc: Paul Mackerras <paulus@samba•org>,
tglx@linutronix•de, linuxppc-dev@lists•ozlabs.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH 03/34 v3] powerpc: Use CONFIG_PREEMPTION
Date: Tue, 12 Nov 2019 23:38:33 +1100 [thread overview]
Message-ID: <874kz92rsm.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20191024160458.vlnf3wlcyjl2ich7@linutronix.de>
Sebastian Andrzej Siewior <bigeasy@linutronix•de> writes:
> From: Thomas Gleixner <tglx@linutronix•de>
>
> CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_RT.
> Both PREEMPT and PREEMPT_RT require the same functionality which today
> depends on CONFIG_PREEMPT.
>
> Switch the entry code over to use CONFIG_PREEMPTION.
>
> Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> Cc: Paul Mackerras <paulus@samba•org>
> Cc: Michael Ellerman <mpe@ellerman•id.au>
> Cc: linuxppc-dev@lists•ozlabs.org
> Signed-off-by: Thomas Gleixner <tglx@linutronix•de>
> [bigeasy: +Kconfig]
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
> ---
> v2…v3: Don't mention die.c changes in the description.
> v1…v2: Remove the changes to die.c.
Acked-by: Michael Ellerman <mpe@ellerman•id.au>
cheers
next prev parent reply other threads:[~2019-11-12 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191015191821.11479-1-bigeasy@linutronix.de>
2019-10-15 19:17 ` [PATCH 03/34] powerpc: Use CONFIG_PREEMPTION Sebastian Andrzej Siewior
2019-10-16 4:57 ` Christophe Leroy
2019-10-16 7:48 ` Sebastian Andrzej Siewior
2019-10-16 9:33 ` Michael Ellerman
2019-10-16 9:35 ` Sebastian Andrzej Siewior
2019-10-24 13:59 ` [PATCH 03/34 v2] " Sebastian Andrzej Siewior
2019-10-24 16:04 ` [PATCH 03/34 v3] " Sebastian Andrzej Siewior
2019-11-12 12:38 ` Michael Ellerman [this message]
2019-12-08 14:58 ` [tip: sched/urgent] sched/rt, " tip-bot2 for 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=874kz92rsm.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=bigeasy@linutronix$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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