All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Valentin Schneider <valentin.schneider@arm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-rt-users@vger.kernel.org,
	Linux PM <linux-pm@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Ingo Molnar <mingo@kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v3 0/2] cpu_pm: cpu_pm_notifier_chain vs PREEMPT_RT
Date: Mon, 16 Aug 2021 18:56:23 +0200	[thread overview]
Message-ID: <CAJZ5v0jOWkWEhdKJ31jq02nFWLG9g+X-NyR3jSgcQ5YfM1WcuQ@mail.gmail.com> (raw)
In-Reply-To: <20210812071339.fm6kt7wugewxo3al@linutronix.de>

On Thu, Aug 12, 2021 at 9:13 AM Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2021-08-11 21:14:30 [+0100], Valentin Schneider wrote:
> > Hi folks,
> >
> > This is v3 of:
> >
> >   http://lore.kernel.org/r/20210811131405.1731576-1-valentin.schneider@arm.com
> >
> > which addresses cpu_pm's notifier chain not playing nice with PREEMPT_RT.
>
> Thank you.
> Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

Both patches applied as 5.15 material, thanks!

      reply	other threads:[~2021-08-16 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 20:14 [PATCH v3 0/2] cpu_pm: cpu_pm_notifier_chain vs PREEMPT_RT Valentin Schneider
2021-08-11 20:14 ` [PATCH v3 1/2] cpu_pm: Make notifier chain use a raw_spinlock_t Valentin Schneider
2021-08-11 20:14 ` [PATCH v3 2/2] notifier: Remove atomic_notifier_call_chain_robust() Valentin Schneider
2021-08-12  7:13 ` [PATCH v3 0/2] cpu_pm: cpu_pm_notifier_chain vs PREEMPT_RT Sebastian Andrzej Siewior
2021-08-16 16:56   ` Rafael J. Wysocki [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=CAJZ5v0jOWkWEhdKJ31jq02nFWLG9g+X-NyR3jSgcQ5YfM1WcuQ@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bristot@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    --cc=valentin.schneider@arm.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.