From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH] rtc: rtc-vr41xx: remove unused function
Date: Tue, 1 Mar 2016 16:20:34 +0100 [thread overview]
Message-ID: <20160301152034.GA23985@piout.net> (raw)
In-Reply-To: <20160301145558.GC26201@ulmo>
On 01/03/2016 at 15:55:58 +0100, Thierry Reding wrote :
> On Tue, Mar 01, 2016 at 06:26:21PM +0530, Sudip Mukherjee wrote:
> > We were getting build warning about:
> > drivers/rtc/rtc-vr41xx.c:228:12: warning: =E2=80=98vr41xx_rtc_alarm_irq=
_enable=E2=80=99
> > defined but not used
> >=20
> > The function vr41xx_rtc_alarm_irq_enable() was not used anywhere.
> >=20
> > Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> > ---
> >=20
> > build log is at:
> > https://travis-ci.org/sudipm-mukherjee/parport/jobs/112780206
> >=20
> > drivers/rtc/rtc-vr41xx.c | 18 ------------------
> > 1 file changed, 18 deletions(-)
> >=20
> > diff --git a/drivers/rtc/rtc-vr41xx.c b/drivers/rtc/rtc-vr41xx.c
> > index f64c282..68cb63e 100644
> > --- a/drivers/rtc/rtc-vr41xx.c
> > +++ b/drivers/rtc/rtc-vr41xx.c
> > @@ -225,24 +225,6 @@ static int vr41xx_rtc_ioctl(struct device *dev, un=
signed int cmd, unsigned long
> > return 0;
> > }
> > =20
> > -static int vr41xx_rtc_alarm_irq_enable(struct device *dev, unsigned in=
t enabled)
> > -{
> > - spin_lock_irq(&rtc_lock);
> > - if (enabled) {
> > - if (!alarm_enabled) {
> > - enable_irq(aie_irq);
> > - alarm_enabled =3D 1;
> > - }
> > - } else {
> > - if (alarm_enabled) {
> > - disable_irq(aie_irq);
> > - alarm_enabled =3D 0;
> > - }
> > - }
> > - spin_unlock_irq(&rtc_lock);
> > - return 0;
> > -}
> > -
>=20
> I don't think it's supposed to be unused, rather back at the time it
> simply wasn't hooked up to the rtc_class_ops.
>=20
> Here's what I used.
>=20
I've already applied the patch from Geert which does the same.
--=20
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--=20
--=20
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---=20
You received this message because you are subscribed to the Google Groups "=
rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [PATCH] rtc: rtc-vr41xx: remove unused function
Date: Tue, 1 Mar 2016 16:20:34 +0100 [thread overview]
Message-ID: <20160301152034.GA23985@piout.net> (raw)
In-Reply-To: <20160301145558.GC26201@ulmo>
On 01/03/2016 at 15:55:58 +0100, Thierry Reding wrote :
> On Tue, Mar 01, 2016 at 06:26:21PM +0530, Sudip Mukherjee wrote:
> > We were getting build warning about:
> > drivers/rtc/rtc-vr41xx.c:228:12: warning: ‘vr41xx_rtc_alarm_irq_enable’
> > defined but not used
> >
> > The function vr41xx_rtc_alarm_irq_enable() was not used anywhere.
> >
> > Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> > ---
> >
> > build log is at:
> > https://travis-ci.org/sudipm-mukherjee/parport/jobs/112780206
> >
> > drivers/rtc/rtc-vr41xx.c | 18 ------------------
> > 1 file changed, 18 deletions(-)
> >
> > diff --git a/drivers/rtc/rtc-vr41xx.c b/drivers/rtc/rtc-vr41xx.c
> > index f64c282..68cb63e 100644
> > --- a/drivers/rtc/rtc-vr41xx.c
> > +++ b/drivers/rtc/rtc-vr41xx.c
> > @@ -225,24 +225,6 @@ static int vr41xx_rtc_ioctl(struct device *dev, unsigned int cmd, unsigned long
> > return 0;
> > }
> >
> > -static int vr41xx_rtc_alarm_irq_enable(struct device *dev, unsigned int enabled)
> > -{
> > - spin_lock_irq(&rtc_lock);
> > - if (enabled) {
> > - if (!alarm_enabled) {
> > - enable_irq(aie_irq);
> > - alarm_enabled = 1;
> > - }
> > - } else {
> > - if (alarm_enabled) {
> > - disable_irq(aie_irq);
> > - alarm_enabled = 0;
> > - }
> > - }
> > - spin_unlock_irq(&rtc_lock);
> > - return 0;
> > -}
> > -
>
> I don't think it's supposed to be unused, rather back at the time it
> simply wasn't hooked up to the rtc_class_ops.
>
> Here's what I used.
>
I've already applied the patch from Geert which does the same.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-01 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 12:56 [rtc-linux] [PATCH] rtc: rtc-vr41xx: remove unused function Sudip Mukherjee
2016-03-01 12:56 ` Sudip Mukherjee
2016-03-01 14:55 ` [rtc-linux] " Thierry Reding
2016-03-01 14:55 ` Thierry Reding
2016-03-01 15:20 ` Alexandre Belloni [this message]
2016-03-01 15:20 ` 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=20160301152034.GA23985@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=thierry.reding@gmail.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 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.