Linux C-SKY architecture development
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: guoren <guoren@kernel.org>
Cc: "linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Linux-Arch <linux-arch@vger.kernel.org>,
	"Guo Ren" <guoren@linux.alibaba.com>,
	"Arnd Bergmann" <arnd@kernel.org>
Subject: Re: [PATCH] csky: Fixup -Wmissing-prototypes warning
Date: Fri, 11 Aug 2023 09:32:59 +0200	[thread overview]
Message-ID: <cf25b0f4-ee4b-40bd-a928-afdc4cad5c2e@app.fastmail.com> (raw)
In-Reply-To: <20230811030750.1335526-1-guoren@kernel.org>

On Fri, Aug 11, 2023, at 05:07, guoren@kernel.org wrote:
>
> Link: https://lore.kernel.org/lkml/20230810141947.1236730-17-arnd@kernel.org/
> Reported-by: Arnd Bergmann <arnd@kernel.org>
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>

Thanks for addressing these!

Reviewed-by: Arnd Bergmann <arnd@arndb.de>

> --- a/arch/csky/kernel/vdso/vgettimeofday.c
> +++ b/arch/csky/kernel/vdso/vgettimeofday.c
> @@ -3,24 +3,35 @@
>  #include <linux/time.h>
>  #include <linux/types.h>
> 
> +extern
> +int __vdso_clock_gettime(clockid_t clock,
> +			 struct old_timespec32 *ts);
>  int __vdso_clock_gettime(clockid_t clock,
>  			 struct old_timespec32 *ts)
>  {
>  	return __cvdso_clock_gettime32(clock, ts);
>  }
> 

This works, but it would be a bit nicer to move the
declarations into a header. I see that we already handle
this in three different ways across x86, arm and arm64,
and you picked method from x86 (and loongarch) here, so
I can't really complain.

What we should probably have instead is a new header
in include/vdso/ that  declares the functions for
every architecture.

      Arnd

  reply	other threads:[~2023-08-11  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  3:07 [PATCH] csky: Fixup -Wmissing-prototypes warning guoren
2023-08-11  7:32 ` Arnd Bergmann [this message]
2023-08-11  8:13   ` Guo Ren
2023-08-30  8:11 ` Guenter Roeck
2023-08-30  9:24   ` Guo Ren

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=cf25b0f4-ee4b-40bd-a928-afdc4cad5c2e@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-csky@vger.kernel.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