[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201102170443.GA4494@osiris>
Date: Mon, 2 Nov 2020 18:04:43 +0100
From: Heiko Carstens <hca@...ux.ibm.com>
To: Qian Cai <cai@...hat.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, peterz@...radead.org,
oleg@...hat.com, tglx@...utronix.de,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux-Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: [PATCH] s390: add support for TIF_NOTIFY_SIGNAL
On Mon, Nov 02, 2020 at 11:59:41AM -0500, Qian Cai wrote:
> On Sun, 2020-11-01 at 17:31 +0000, Heiko Carstens wrote:
> > On Thu, Oct 29, 2020 at 10:21:11AM -0600, Jens Axboe wrote:
> > > Wire up TIF_NOTIFY_SIGNAL handling for s390.
> > >
> > > Cc: linux-s390@...r.kernel.org
> > > Signed-off-by: Jens Axboe <axboe@...nel.dk>
>
> Even though I did confirm that today's linux-next contains this additional patch
> from Heiko below, a z10 guest is still unable to boot. Reverting the whole
> series (reverting only "s390: add support for TIF_NOTIFY_SIGNAL" introduced
> compiling errors) fixed the problem, i.e., git revert --no-edit
> af0dd809f3d3..7b074c15374c [1]
>
> .config: https://cailca.coding.net/public/linux/mm/git/files/master/s390.config
I'll take a look at it, but probably not today anymore.
Powered by blists - more mailing lists