From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH REPOST v3 0/2] signal: Avoid preempt_disable() in ptrace_stop() on PREEMPT_RT
Date: Thu, 17 Aug 2023 15:46:32 +0200 [thread overview]
Message-ID: <20230817134632.jbAX7yo1@linutronix.de> (raw)
In-Reply-To: <20230803100932.325870-1-bigeasy@linutronix.de>
On 2023-08-03 12:09:30 [+0200], To linux-kernel@vger.kernel.org wrote:
> this mini series updates the comment to properly explain why the
> preempt-disable section has been added and then disables this on
> PREEMPT_RT explaining why it can not be done.
ping …
> v3…v1
> - Include the update comment of the second patch which was posted as
> v2 within the orignal thread.
> - Add Oleg's Acks.
>
> This is the repost of
> https://lore.kernel.org/20230615105627.1311437-1-bigeasy@linutronix.de
>
> Previous post:
> https://lore.kernel.org/20230606085524.2049961-1-bigeasy@linutronix.de
Sebastian
prev parent reply other threads:[~2023-08-17 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 10:09 [PATCH REPOST v3 0/2] signal: Avoid preempt_disable() in ptrace_stop() on PREEMPT_RT Sebastian Andrzej Siewior
2023-08-03 10:09 ` [PATCH 1/2] signal: Add proper comment about the preempt-disable in ptrace_stop() Sebastian Andrzej Siewior
2023-09-19 20:16 ` [tip: core/core] signal: Add a proper comment about preempt_disable() " tip-bot2 for Sebastian Andrzej Siewior
2023-09-20 6:57 ` Ingo Molnar
2023-09-20 7:47 ` [PATCH] signal: Correct spelling typos " Sebastian Andrzej Siewior
2023-08-03 10:09 ` [PATCH 2/2] signal: Don't disable preemption in ptrace_stop() on PREEMPT_RT Sebastian Andrzej Siewior
2023-09-19 20:16 ` [tip: core/core] " tip-bot2 for Sebastian Andrzej Siewior
2023-08-17 13:46 ` Sebastian Andrzej Siewior [this message]
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=20230817134632.jbAX7yo1@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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