From: Will Deacon <will@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: add support for TIF_NOTIFY_SIGNAL
Date: Fri, 30 Oct 2020 06:48:51 +0000 [thread overview]
Message-ID: <20201030064850.GA31933@willie-the-truck> (raw)
In-Reply-To: <111f501e-33e7-ad38-6476-9874f1226ad7@kernel.dk>
Hi Jens,
[+ Catalin]
On Thu, Oct 29, 2020 at 10:11:55AM -0600, Jens Axboe wrote:
> Cc: linux-arm-kernel@lists.infradead.org
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> ---
>
> 5.11 has support queued up for TIF_NOTIFY_SIGNAL, see this posting
> for details:
>
> https://lore.kernel.org/io-uring/20201026203230.386348-1-axboe@kernel.dk/
>
> As part of that work, I'm adding TIF_NOTIFY_SIGNAL support to all archs,
> as that will enable a set of cleanups once all of them support it. I'm
> happy carrying this patch if need be, or it can be funelled through the
> arch tree. Let me know.
>
> arch/arm64/include/asm/thread_info.h | 5 ++++-
> arch/arm64/kernel/signal.c | 2 +-
> 2 files changed, 5 insertions(+), 2 deletions(-)
I think it makes sense for this to go via the arm64 tree, as it's
self-contained and we can handle any conflicts directly. Catalin -- would
you be able to pick this up when you start queueing stuff around -rc3,
please?
But either way:
Acked-by: Will Deacon <will@kernel.org>
Cheers,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-30 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:11 [PATCH] arm64: add support for TIF_NOTIFY_SIGNAL Jens Axboe
2020-10-30 6:48 ` Will Deacon [this message]
2020-10-30 13:22 ` Jens Axboe
2020-11-05 16:19 ` Jens Axboe
2020-11-06 12:14 ` Catalin Marinas
2020-11-06 14:38 ` Jens Axboe
2020-11-06 14:41 ` Catalin Marinas
2020-11-06 14:55 ` Jens Axboe
2020-11-06 14:59 ` Catalin Marinas
2020-11-06 15:00 ` 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=20201030064850.GA31933@willie-the-truck \
--to=will@kernel.org \
--cc=axboe@kernel.dk \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox