From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v4 4/4] MIPS: Add identifier names to arguments of die() declaration
Date: Sat, 19 Aug 2023 12:49:33 +0200 [thread overview]
Message-ID: <d138c76c-72d9-f07e-7db0-1e5e939bee9c@linaro.org> (raw)
In-Reply-To: <1692434183-2054-5-git-send-email-yangtiezhu@loongson.cn>
On 19/8/23 10:36, Tiezhu Yang wrote:
> Add identifier names to arguments of die() declaration in ptrace.h
> to fix the following checkpatch warnings:
>
> WARNING: function definition argument 'const char *' should also have an identifier name
> WARNING: function definition argument 'struct pt_regs *' should also have an identifier name
>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> arch/mips/include/asm/ptrace.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-08-19 10:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 8:36 [PATCH v4 0/4] Modify die() for MIPS Tiezhu Yang
2023-08-19 8:36 ` [PATCH v4 1/4] MIPS: Add BUG() at the end of nmi_exception_handler() Tiezhu Yang
2023-08-19 8:36 ` [PATCH v4 2/4] MIPS: Do not kill the task in die() if notify_die() returns NOTIFY_STOP Tiezhu Yang
2023-08-19 8:36 ` [PATCH v4 3/4] MIPS: Return earlier " Tiezhu Yang
2023-08-20 8:53 ` Huacai Chen
2023-08-21 2:28 ` Tiezhu Yang
2023-08-22 7:38 ` Huacai Chen
2023-08-22 8:55 ` Tiezhu Yang
2023-08-19 8:36 ` [PATCH v4 4/4] MIPS: Add identifier names to arguments of die() declaration Tiezhu Yang
2023-08-19 10:49 ` Philippe Mathieu-Daudé [this message]
2023-08-28 9:11 ` [PATCH v4 0/4] Modify die() for MIPS Thomas Bogendoerfer
2023-08-29 15:19 ` Thomas Bogendoerfer
2023-08-30 6:23 ` Huacai Chen
2023-08-30 17:01 ` Maciej W. Rozycki
2023-08-31 5:34 ` YunQiang Su
2023-08-31 10:38 ` Jiaxun Yang
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=d138c76c-72d9-f07e-7db0-1e5e939bee9c@linaro.org \
--to=philmd@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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®