From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] openrisc: time: don't mark comment as kernel-doc
Date: Sat, 2 Oct 2021 21:38:16 +0900 [thread overview]
Message-ID: <YVhSuFFMnlQm+x+8@antec> (raw)
In-Reply-To: <20211001021101.18225-1-rdunlap@infradead.org>
On Thu, Sep 30, 2021 at 07:11:01PM -0700, Randy Dunlap wrote:
> Fix a kernel-doc warning by unmarking the comment as being in
> kernel-doc notation.
>
> Fixes this warning:
> arch/openrisc/kernel/time.c:137: warning: expecting prototype for Clocksource(). Prototype was for openrisc_timer_read() instead
>
> Fixes: b731fbbd246e ("OpenRISC: Timekeeping")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Jonas Bonn <jonas@southpole.se>
> Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> Cc: Stafford Horne <shorne@gmail.com>
> Cc: openrisc at lists.librecores.org
> ---
> arch/openrisc/kernel/time.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20210930.orig/arch/openrisc/kernel/time.c
> +++ linux-next-20210930/arch/openrisc/kernel/time.c
> @@ -127,7 +127,7 @@ irqreturn_t __irq_entry timer_interrupt(
> return IRQ_HANDLED;
> }
>
> -/**
> +/*
> * Clocksource: Based on OpenRISC timer/counter
> *
> * This sets up the OpenRISC Tick Timer as a clock source. The tick timer
Hi Randy,
This looks good to me, thank you. I am queuing it.
-Stafford
WARNING: multiple messages have this Message-ID (diff)
From: Stafford Horne <shorne@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
openrisc@lists.librecores.org
Subject: Re: [PATCH] openrisc: time: don't mark comment as kernel-doc
Date: Sat, 2 Oct 2021 21:38:16 +0900 [thread overview]
Message-ID: <YVhSuFFMnlQm+x+8@antec> (raw)
In-Reply-To: <20211001021101.18225-1-rdunlap@infradead.org>
On Thu, Sep 30, 2021 at 07:11:01PM -0700, Randy Dunlap wrote:
> Fix a kernel-doc warning by unmarking the comment as being in
> kernel-doc notation.
>
> Fixes this warning:
> arch/openrisc/kernel/time.c:137: warning: expecting prototype for Clocksource(). Prototype was for openrisc_timer_read() instead
>
> Fixes: b731fbbd246e ("OpenRISC: Timekeeping")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Jonas Bonn <jonas@southpole.se>
> Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> Cc: Stafford Horne <shorne@gmail.com>
> Cc: openrisc@lists.librecores.org
> ---
> arch/openrisc/kernel/time.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20210930.orig/arch/openrisc/kernel/time.c
> +++ linux-next-20210930/arch/openrisc/kernel/time.c
> @@ -127,7 +127,7 @@ irqreturn_t __irq_entry timer_interrupt(
> return IRQ_HANDLED;
> }
>
> -/**
> +/*
> * Clocksource: Based on OpenRISC timer/counter
> *
> * This sets up the OpenRISC Tick Timer as a clock source. The tick timer
Hi Randy,
This looks good to me, thank you. I am queuing it.
-Stafford
next prev parent reply other threads:[~2021-10-02 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 2:11 [OpenRISC] [PATCH] openrisc: time: don't mark comment as kernel-doc Randy Dunlap
2021-10-01 2:11 ` Randy Dunlap
2021-10-02 12:38 ` Stafford Horne [this message]
2021-10-02 12:38 ` Stafford Horne
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=YVhSuFFMnlQm+x+8@antec \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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 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.