From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
uclinux-h8-devel@lists.sourceforge.jp
Subject: Re: [PATCH] arch/h8300: eliminate ptrace.h warnings
Date: Sun, 22 Jul 2018 22:33:15 +0900 [thread overview]
Message-ID: <87lga3fl9g.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <c08b3519-0e43-98ff-1e09-397bcfd55270@infradead.org>
On Fri, 20 Jul 2018 11:34:53 +0900,
Randy Dunlap wrote:
>
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Add a "struct task_struct;" stub to arch/h8300's ptrace.h header to
> eliminate gcc warnings (gcc version is 8.1.0).
>
> ../arch/h8300/include/asm/ptrace.h:32:34: warning: 'struct task_struct' declared inside parameter list will not be visible outside of this definition or declaration
> extern long h8300_get_reg(struct task_struct *task, int regno);
> ../arch/h8300/include/asm/ptrace.h:33:33: warning: 'struct task_struct' declared inside parameter list will not be visible outside of this definition or declaration
> extern int h8300_put_reg(struct task_struct *task, int regno,
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> Cc: uclinux-h8-devel@lists.sourceforge.jp
> ---
> arch/h8300/include/asm/ptrace.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-next-20180717.orig/arch/h8300/include/asm/ptrace.h
> +++ linux-next-20180717/arch/h8300/include/asm/ptrace.h
> @@ -4,6 +4,8 @@
>
> #include <uapi/asm/ptrace.h>
>
> +struct task_struct;
> +
> #ifndef __ASSEMBLY__
> #ifndef PS_S
> #define PS_S (0x10)
>
>
Applied to h8300-next.
Thanks.
--
Yosinori Sato
prev parent reply other threads:[~2018-07-22 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 2:34 [PATCH] arch/h8300: eliminate ptrace.h warnings Randy Dunlap
2018-07-22 13:33 ` Yoshinori Sato [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=87lga3fl9g.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
/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.