From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-riscv@lists.infradead.org
Subject: rcu: Make expedited GPs handle CPU 0 being offline
Date: Thu, 6 Sep 2018 20:45:30 -0700 [thread overview]
Message-ID: <20180907034530.GA18753@linux.vnet.ibm.com> (raw)
Hello!
Please apply the following commit to the v4.18 -stable tree:
rcu: Make expedited GPs handle CPU 0 being offline
fcc63543650150629c8a873cbef3578770acecd9
This patch fixes a v4.18 regression that is causing the RISC-V people
(CCed) some trouble. It is a small patch and has been tested in the
failing situation running v4.18 by Atish Patra and Andreas Schwab
(both CCed).
Please let me know if more information is required.
Thanx, Paul
WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: stable@vger.kernel.org
Cc: atish.patra@wdc.com, hch@infradead.org, schwab@suse.de,
linux-riscv@lists.infradead.org, palmer@sifive.com,
boqun.feng@gmail.com
Subject: rcu: Make expedited GPs handle CPU 0 being offline
Date: Thu, 6 Sep 2018 20:45:30 -0700 [thread overview]
Message-ID: <20180907034530.GA18753@linux.vnet.ibm.com> (raw)
Hello!
Please apply the following commit to the v4.18 -stable tree:
rcu: Make expedited GPs handle CPU 0 being offline
fcc63543650150629c8a873cbef3578770acecd9
This patch fixes a v4.18 regression that is causing the RISC-V people
(CCed) some trouble. It is a small patch and has been tested in the
failing situation running v4.18 by Atish Patra and Andreas Schwab
(both CCed).
Please let me know if more information is required.
Thanx, Paul
next reply other threads:[~2018-09-07 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 3:45 Paul E. McKenney [this message]
2018-09-07 3:45 ` rcu: Make expedited GPs handle CPU 0 being offline Paul E. McKenney
2018-09-07 5:47 ` Greg KH
2018-09-07 5:47 ` Greg KH
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=20180907034530.GA18753@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-riscv@lists.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.