All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: add support for TIF_NOTIFY_SIGNAL
Date: Sun, 1 Nov 2020 14:15:22 +0100	[thread overview]
Message-ID: <20201101131522.GA4111@alpha.franken.de> (raw)
In-Reply-To: <116773a7-acc4-0f18-9249-532a844502ef@kernel.dk>

On Thu, Oct 29, 2020 at 10:16:53AM -0600, Jens Axboe wrote:
> Wire up TIF_NOTIFY_SIGNAL handling for mips.
> 
> Cc: linux-mips@vger.kernel.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/mips/include/asm/thread_info.h | 4 +++-
>  arch/mips/kernel/signal.c           | 2 +-
>  2 files changed, 4 insertions(+), 2 deletions(-)

Acked-By: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

Please take the patch into your tree.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2020-11-01 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 16:16 [PATCH] mips: add support for TIF_NOTIFY_SIGNAL Jens Axboe
2020-11-01 13:15 ` Thomas Bogendoerfer [this message]
2020-11-01 14:04   ` 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=20201101131522.GA4111@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=axboe@kernel.dk \
    --cc=linux-mips@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 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.