From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Greg Kurz <groug@kaod.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Cc: , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries: Fix xive=off command line
Date: Wed, 15 May 2019 10:54:42 +0000 [thread overview]
Message-ID: <20190515105443.835E72084E@mail.kernel.org> (raw)
In-Reply-To: <155791470178.432724.8008395673479905061.stgit@bahia.lan>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: eac1e731b59e powerpc/xive: guest exploitation of the XIVE interrupt controller.
The bot has tested the following trees: v5.1.1, v5.0.15, v4.19.42, v4.14.118.
v5.1.1: Build OK!
v5.0.15: Build OK!
v4.19.42: Failed to apply! Possible dependencies:
8ca2d5151e7f ("powerpc/prom_init: Move a few remaining statics to appropriate sections")
c886087caee7 ("powerpc/prom_init: Move prom_radix_disable to __prombss")
v4.14.118: Failed to apply! Possible dependencies:
028555a590d6 ("powerpc/xive: fix hcall H_INT_RESET to support long busy delays")
7a22d6321c3d ("powerpc/mm/radix: Update command line parsing for disable_radix")
8ca2d5151e7f ("powerpc/prom_init: Move a few remaining statics to appropriate sections")
c886087caee7 ("powerpc/prom_init: Move prom_radix_disable to __prombss")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-15 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 10:05 [PATCH] powerpc/pseries: Fix xive=off command line Greg Kurz
2019-05-15 10:13 ` Cédric Le Goater
2019-05-15 10:54 ` Sasha Levin [this message]
2019-05-17 10:57 ` Greg Kurz
2019-06-03 12:32 ` Michael Ellerman
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=20190515105443.835E72084E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).