From: Will Deacon <will.deacon@arm.com>
To: Julien Grall <julien.grall@arm.com>
Cc: linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] arm64: Remove documentation about TIF_USEDFPU
Date: Mon, 11 Feb 2019 11:18:28 +0000 [thread overview]
Message-ID: <20190211111828.GD30880@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <20190208170425.10891-4-julien.grall@arm.com>
On Fri, Feb 08, 2019 at 05:04:25PM +0000, Julien Grall wrote:
> TIF_USEDFPU is not defined as thread flags for Arm64. So drop it from
> the documentation.
>
> Signed-off-by: Julien Grall <julien.grall@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> arch/arm64/include/asm/thread_info.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/include/asm/thread_info.h b/arch/arm64/include/asm/thread_info.h
> index bbca68b54732..eb3ef73e07cf 100644
> --- a/arch/arm64/include/asm/thread_info.h
> +++ b/arch/arm64/include/asm/thread_info.h
> @@ -79,7 +79,6 @@ void arch_release_task_struct(struct task_struct *tsk);
> * TIF_SIGPENDING - signal pending
> * TIF_NEED_RESCHED - rescheduling necessary
> * TIF_NOTIFY_RESUME - callback before returning to user
> - * TIF_USEDFPU - FPU was used by this task this quantum (SMP)
> */
> #define TIF_SIGPENDING 0
> #define TIF_NEED_RESCHED 1
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2019-02-11 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 17:04 [PATCH RESEND 0/3] Remove reference of TIF_USEDFPU on arch not using it Julien Grall
2019-02-08 17:04 ` [PATCH 1/3] nds32: Removed unused thread flag TIF_USEDFPU Julien Grall
2019-02-08 17:04 ` [PATCH 2/3] arm: Remove documentation about TIF_USEDFPU Julien Grall
2019-02-08 17:04 ` [PATCH 3/3] arm64: " Julien Grall
2019-02-11 11:18 ` Will Deacon [this message]
2019-02-26 16:41 ` Catalin Marinas
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=20190211111828.GD30880@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=julien.grall@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®