From: <Conor.Dooley@microchip.com>
To: <trix@redhat.com>, <Lewis.Hanly@microchip.com>,
<a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<Daire.McNamara@microchip.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-rtc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: remove 'pending' variable from mpfs_rtc_wakeup_irq_handler()
Date: Tue, 28 Jun 2022 07:12:53 +0000 [thread overview]
Message-ID: <17cba42b-0345-fdb2-69e3-cfc3f310c2f1@microchip.com> (raw)
In-Reply-To: <20220627205943.2075043-1-trix@redhat.com>
On 27/06/2022 21:59, Tom Rix wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> cppcheck reports
> [drivers/rtc/rtc-mpfs.c:219]: (style) Variable 'pending' is assigned a value that is never used.
>
> The fetched CONTROL_REG stored in pending is unused and partially
> duplicates the functionality of the later call to mpfs_rtc_clear(). This looks
> like leftover development code, so remove pending.
It predates my involvement with the driver so I am not sure why
exactly it was introduced, but it looks to me to be surplus to
requirements.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> Fixes: 0b31d703598d ("rtc: Add driver for Microchip PolarFire SoC")
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/rtc/rtc-mpfs.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/rtc/rtc-mpfs.c b/drivers/rtc/rtc-mpfs.c
> index db9c638e50f7..f14d1925e0c9 100644
> --- a/drivers/rtc/rtc-mpfs.c
> +++ b/drivers/rtc/rtc-mpfs.c
> @@ -213,10 +213,7 @@ static inline struct clk *mpfs_rtc_init_clk(struct device *dev)
> static irqreturn_t mpfs_rtc_wakeup_irq_handler(int irq, void *dev)
> {
> struct mpfs_rtc_dev *rtcdev = dev;
> - unsigned long pending;
>
> - pending = readl(rtcdev->base + CONTROL_REG);
> - pending &= CONTROL_ALARM_ON_BIT;
> mpfs_rtc_clear_irq(rtcdev);
>
> rtc_update_irq(rtcdev->rtc, 1, RTC_IRQF | RTC_AF);
> --
> 2.27.0
>
next prev parent reply other threads:[~2022-06-28 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 20:59 [PATCH] rtc: remove 'pending' variable from mpfs_rtc_wakeup_irq_handler() Tom Rix
2022-06-28 7:12 ` Conor.Dooley [this message]
2022-07-26 14:22 ` Alexandre Belloni
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=17cba42b-0345-fdb2-69e3-cfc3f310c2f1@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=Lewis.Hanly@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=trix@redhat.com \
/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