linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: add support for TIF_NOTIFY_SIGNAL
Date: Sun, 1 Nov 2020 07:04:01 -0700	[thread overview]
Message-ID: <c818c023-de40-bca7-7f33-06cc917a6d6c@kernel.dk> (raw)
In-Reply-To: <20201101131522.GA4111@alpha.franken.de>

On 11/1/20 6:15 AM, Thomas Bogendoerfer wrote:
> 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.

Thanks, added your acked-by.

-- 
Jens Axboe


      reply	other threads:[~2020-11-01 14:04 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
2020-11-01 14:04   ` Jens Axboe [this message]

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=c818c023-de40-bca7-7f33-06cc917a6d6c@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).