From: Igor Grinberg <grinberg@compulab.co.il>
To: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com, ohad@wizery.com
Subject: Re: [PATCH] BUILD FIX:hwspinlock: do not return any value from void funtion
Date: Mon, 07 Nov 2011 15:07:25 +0200 [thread overview]
Message-ID: <4EB7D80D.2080108@compulab.co.il> (raw)
In-Reply-To: <1320670686-29286-1-git-send-email-hvaibhav@ti.com>
Hi Vaibhav,
On 11/07/11 14:58, Vaibhav Hiremath wrote:
> Fixes below compilation error -
>
> CC arch/arm/mach-omap2/hwspinlock.o
> cc1: warnings being treated as errors
> In file included from arch/arm/mach-omap2/hwspinlock.c:22:0:
> include/linux/hwspinlock.h: In function '__hwspin_unlock':
> include/linux/hwspinlock.h:121:2: error: 'return' with a value, in function
> returning void
> make[1]: *** [arch/arm/mach-omap2/hwspinlock.o] Error 1
> make: *** [arch/arm/mach-omap2] Error 2
>
> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> ---
> include/linux/hwspinlock.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/hwspinlock.h b/include/linux/hwspinlock.h
> index 08a2fee..192710a 100644
> --- a/include/linux/hwspinlock.h
> +++ b/include/linux/hwspinlock.h
> @@ -118,7 +118,7 @@ int __hwspin_trylock(struct hwspinlock *hwlock, int mode, unsigned long *flags)
> static inline
> void __hwspin_unlock(struct hwspinlock *hwlock, int mode, unsigned long *flags)
> {
> - return 0;
> + return;
Isn't it better to just remove this line?
> }
>
> static inline int hwspin_lock_get_id(struct hwspinlock *hwlock)
--
Regards,
Igor.
next prev parent reply other threads:[~2011-11-07 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 12:58 [PATCH] BUILD FIX:hwspinlock: do not return any value from void funtion Vaibhav Hiremath
2011-11-07 13:07 ` Igor Grinberg [this message]
2011-11-07 13:40 ` Hiremath, Vaibhav
2011-11-07 13:55 ` Ohad Ben-Cohen
2011-11-07 13:58 ` Hiremath, Vaibhav
2011-11-07 14:01 ` Ohad Ben-Cohen
2011-11-07 14:03 ` Hiremath, Vaibhav
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=4EB7D80D.2080108@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=hvaibhav@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=tony@atomide.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.