From: Heiko Carstens <hca@linux.ibm.com>
To: Qian Cai <cai@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, oleg@redhat.com, tglx@linutronix.de,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] s390: add support for TIF_NOTIFY_SIGNAL
Date: Mon, 2 Nov 2020 18:04:43 +0100 [thread overview]
Message-ID: <20201102170443.GA4494@osiris> (raw)
In-Reply-To: <362e3645e2c0891309c07e244a147f0c32f106da.camel@redhat.com>
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@vger.kernel.org
> > > Signed-off-by: Jens Axboe <axboe@kernel.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.
next prev parent reply other threads:[~2020-11-02 17:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201101173153.GC9375 () osiris>
2020-11-02 16:59 ` [PATCH] s390: add support for TIF_NOTIFY_SIGNAL Qian Cai
2020-11-02 17:04 ` Heiko Carstens [this message]
2020-11-02 17:07 ` Jens Axboe
2020-11-02 18:58 ` Qian Cai
2020-11-02 19:50 ` Jens Axboe
2020-11-02 21:15 ` Qian Cai
[not found] <54c02fa6-8c8a-667f-af99-e83a1f150586 () kernel ! dk>
2020-11-03 10:54 ` Sven Schnelle
2020-10-29 16:21 Jens Axboe
2020-11-01 17:31 ` Heiko Carstens
2020-11-01 18:58 ` Jens Axboe
2020-11-03 11:00 ` Sven Schnelle
2020-11-03 14:09 ` Jens Axboe
2020-11-03 15:03 ` Sven Schnelle
2020-11-03 15:12 ` Jens Axboe
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=20201102170443.GA4494@osiris \
--to=hca@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=cai@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--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 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.