From: Mark Rutland <mark.rutland@arm.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Move TIF_* documentation to individual definitions
Date: Wed, 31 Jul 2019 16:01:38 +0100 [thread overview]
Message-ID: <20190731150137.GE39768@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190731133520.17939-1-geert+renesas@glider.be>
On Wed, Jul 31, 2019 at 03:35:20PM +0200, Geert Uytterhoeven wrote:
> Some TIF_* flags are documented in the comment block at the top, some
> next to their definitions, some in both places.
>
> Move all documentation to the individual definitions for consistency,
> and for easy lookup.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> The alternative is to move all of them to the comment block, and using
> linuxdoc style.
>
> arch/arm64/include/asm/thread_info.h | 24 ++++++++----------------
> 1 file changed, 8 insertions(+), 16 deletions(-)
>
> diff --git a/arch/arm64/include/asm/thread_info.h b/arch/arm64/include/asm/thread_info.h
> index 180b34ec59650a9b..cb3eb1ccccc4116b 100644
> --- a/arch/arm64/include/asm/thread_info.h
> +++ b/arch/arm64/include/asm/thread_info.h
> @@ -60,28 +60,20 @@ void arch_release_task_struct(struct task_struct *tsk);
> #endif
>
> /*
> - * thread information flags:
> - * TIF_SYSCALL_TRACE - syscall trace active
> - * TIF_SYSCALL_TRACEPOINT - syscall tracepoint for ftrace
> - * TIF_SYSCALL_AUDIT - syscall auditing
> - * TIF_SECCOMP - syscall secure computing
> - * TIF_SYSCALL_EMU - syscall emulation active
> - * TIF_SIGPENDING - signal pending
> - * TIF_NEED_RESCHED - rescheduling necessary
> - * TIF_NOTIFY_RESUME - callback before returning to user
> + * thread information flags
> */
We can probably just get rid of the this comment block at this point. :)
> -#define TIF_SIGPENDING 0
> -#define TIF_NEED_RESCHED 1
> +#define TIF_SIGPENDING 0 /* signal pending */
> +#define TIF_NEED_RESCHED 1 /* rescheduling necessary */
> #define TIF_NOTIFY_RESUME 2 /* callback before returning to user */
> #define TIF_FOREIGN_FPSTATE 3 /* CPU's FP state is not current's */
> #define TIF_UPROBE 4 /* uprobe breakpoint or singlestep */
> #define TIF_FSCHECK 5 /* Check FS is USER_DS on return */
> #define TIF_NOHZ 7
> -#define TIF_SYSCALL_TRACE 8
> -#define TIF_SYSCALL_AUDIT 9
> -#define TIF_SYSCALL_TRACEPOINT 10
> -#define TIF_SECCOMP 11
> -#define TIF_SYSCALL_EMU 12
> +#define TIF_SYSCALL_TRACE 8 /* syscall trace active */
> +#define TIF_SYSCALL_AUDIT 9 /* syscall auditing */
> +#define TIF_SYSCALL_TRACEPOINT 10 /* syscall tracepoint for ftrace */
> +#define TIF_SECCOMP 11 /* syscall secure computing */
> +#define TIF_SYSCALL_EMU 12 /* syscall emulation active */
> #define TIF_MEMDIE 18 /* is terminating due to OOM killer */
> #define TIF_FREEZE 19
> #define TIF_RESTORE_SIGMASK 20
FWIW this looks sane to me, so:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-07-31 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 13:35 Geert Uytterhoeven
2019-07-31 15:01 ` Mark Rutland [this message]
2019-07-31 16:14 ` Will Deacon
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=20190731150137.GE39768@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=wad@chromium.org \
--cc=will@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®