From: Catalin Marinas <catalin.marinas@arm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: add support for TIF_NOTIFY_SIGNAL
Date: Fri, 6 Nov 2020 14:41:26 +0000 [thread overview]
Message-ID: <20201106144125.GI29329@gaia> (raw)
In-Reply-To: <5d1de364-9e11-1881-4b7d-ae10bf39f1a4@kernel.dk>
On Fri, Nov 06, 2020 at 07:38:21AM -0700, Jens Axboe wrote:
> On 11/6/20 5:14 AM, Catalin Marinas wrote:
> > On Thu, Nov 05, 2020 at 09:19:49AM -0700, Jens Axboe wrote:
> >> Gentle nudge on this one.
> >
> > I'll pick it up for 5.11, though I only start queuing patches usually at
> > -rc3 (so next week).
>
> Thanks! I can carry it too with your ack, I got some patches that depend
> on all archs being switched over. But not a huge deal if you want to
> take it through your tree, I'll likely need to split into a prep and
> post series anyway.
If you have a dependency, feel free to take it through your tree but
please provide a stable branch in case we get a non-trivial conflict.
Will's ack would suffice but if you need another:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
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-11-06 14:41 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
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 [this message]
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=20201106144125.GI29329@gaia \
--to=catalin.marinas@arm.com \
--cc=axboe@kernel.dk \
--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 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.