From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: vapier@gentoo.org
Cc: john.stultz@linaro.org, linux-kernel@vger.kernel.org,
stable@kernel.org, rtc-linux@googlegroups.com,
a.zummo@towertech.it
Subject: Re: [PATCH] rtc-bfin: add missing "return 0" in new alarm func> On Fri, Mar 18, 2011 at 04:26:24AM -0400, Mike Frysinger wrote:
Date: Sat, 19 Mar 2011 09:15:30 +0800 [thread overview]
Message-ID: <20110319011527.GA1972@gmail.com> (raw)
In-Reply-To: <AANLkTinC_WCh2XXk-irG9d5QZvVU439_FYWZzTGQLbG7@mail.gmail.com>
On Sat, Mar 19, 2011 at 09:10:14AM +0800, jiaweiwei wrote:
>
> >> the end leading to the build warning:
> >> drivers/rtc/rtc-bfin.c: In function 'bfin_rtc_alarm_irq_enable':
> >> drivers/rtc/rtc-bfin.c:253: warning: control reaches end of
> >> non-void function
> >>
> >> CC: stable@kernel.org
> >> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Acked-by: Harry Wei <harryxiyou@gmail.com>
> >> ---
> >> drivers/rtc/rtc-bfin.c | 2 ++
> >> 1 files changed, 2 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/rtc/rtc-bfin.c b/drivers/rtc/rtc-bfin.c
> >> index 17971d9..0e61e2d 100644
> >> --- a/drivers/rtc/rtc-bfin.c
> >> +++ b/drivers/rtc/rtc-bfin.c
> >> @@ -276,6 +276,8 @@ static int bfin_rtc_alarm_irq_enable(struct device
> >> *dev, unsigned int enabled)
> >> bfin_rtc_int_set_alarm(rtc);
> >> else
> >> bfin_rtc_int_clear(~(RTC_ISTAT_ALARM |
> >> RTC_ISTAT_ALARM_DAY));
> >> +
> >> + return 0;
> >> }
> >>
> >> static int bfin_rtc_read_time(struct device *dev, struct rtc_time *tm)
> >> --
> >> 1.7.4.1
> >>
>alarm_irq_enable function forgot to add a "return 0" to
>> the end leading to the build warning:
>> drivers/rtc/rtc-bfin.c: In function 'bfin_rtc_alarm_irq_enable':
>> drivers/rtc/rtc-bfin.c:253: warning: control reaches end of non-void function
>
> I am sure we should give a return-value
> but whether it is '0'? Maybe it should return
> other value.
> Can you give some explanations for yours.
>read the interface.c code ... this func returns 0 on "success". i
>dont know what other possible value this could return.
Oh, it is true.
Thanks.
Best Regards.
Harry Wei.
next prev parent reply other threads:[~2011-03-19 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 8:26 [PATCH] rtc-bfin: add missing "return 0" in new alarm func Mike Frysinger
2011-03-18 14:26 ` Harry Wei
2011-03-18 17:52 ` Mike Frysinger
[not found] ` <AANLkTinjTVpNbkiNKpbc7kvtMVeXfjifr7Q5Dg4B9oGE@mail.gmail.com>
[not found] ` <AANLkTinC_WCh2XXk-irG9d5QZvVU439_FYWZzTGQLbG7@mail.gmail.com>
2011-03-19 1:15 ` Harry Wei [this message]
2011-03-19 1:18 ` John Stultz
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=20110319011527.GA1972@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=a.zummo@towertech.it \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=stable@kernel.org \
--cc=vapier@gentoo.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