From: Qian Cai <cai@redhat•com>
To: Jens Axboe <axboe@kernel•dk>
Cc: linux-s390@vger•kernel.org, Heiko Carstens <hca@linux•ibm.com>,
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, 02 Nov 2020 16:15:34 -0500 [thread overview]
Message-ID: <0bd01646f4b429e89359d0618d25f5d6cf92c4f5.camel@redhat.com> (raw)
In-Reply-To: <b7b2fa41-fab2-7fd4-f10f-9c352bc9c692@kernel.dk>
On Mon, 2020-11-02 at 12:50 -0700, Jens Axboe wrote:
> Ah, but that's because later patches assume that TIF_NOTIFY_SIGNAL is
> always there once all archs have been converted. If you just want to back
> out that patch, you'll need to just revert this one:
>
> commit 82ef6998ed9d488e56bbfbcc2ec9adf62bf78f08
> Author: Jens Axboe <axboe@kernel•dk>
> Date: Fri Oct 9 16:04:39 2020 -0600
>
> kernel: remove checking for TIF_NOTIFY_SIGNAL
>
> as well and I suspect it should build.
No, at the minimal, I'll need to revert those to build successfully.
7b074c15374c io_uring: remove 'twa_signal_ok' deadlock work-around
eb48a0f216fa kernel: remove checking for TIF_NOTIFY_SIGNAL
c634e6b63a81 signal: kill JOBCTL_TASK_WORK
f8b667db31a3 io_uring: JOBCTL_TASK_WORK is no longer used by task_work
4c3d9c3b415a s390: add support for TIF_NOTIFY_SIGNAL
Then, it will fix the boot issue as well.
next prev parent reply other threads:[~2020-11-02 21:15 UTC|newest]
Thread overview: 11+ 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
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 [this message]
[not found] <54c02fa6-8c8a-667f-af99-e83a1f150586 () kernel ! dk>
2020-11-03 10:54 ` Sven Schnelle
[not found] <20201101173153.GC9375@osiris>
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=0bd01646f4b429e89359d0618d25f5d6cf92c4f5.camel@redhat.com \
--to=cai@redhat$(echo .)com \
--cc=axboe@kernel$(echo .)dk \
--cc=hca@linux$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=oleg@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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