From: Yijing Wang <wangyijing@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>,
David Laight <David.Laight@ACULAB.COM>
Cc: 'Tony Prisk' <linux@prisktech.co.nz>,
John Stultz <john.stultz@linaro.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
"linux@lists.openrisc.net" <linux@openrisc.net>,
Sekhar Nori <nsekhar@ti.com>, Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Daniel Walker <dwalker@fifo99.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Jonas Bonn <jonas@southpole.se>,
Kukjin Kim <kgene.kim@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Richard Weinberger <richard@nod.at>,
"x86@kernel.org" <x86@kernel.org>,
Tony Lindgren <tony@atomide.com>, Ingo Molnar <mingo@redhat.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@v>
Subject: Re: [PATCH 2/2] clocksource: Make clocksource register functions void
Date: Mon, 10 Feb 2014 09:13:55 +0800 [thread overview]
Message-ID: <52F827D3.5080906@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402052139560.24986@ionos.tec.linutronix.de>
On 2014/2/6 4:40, Thomas Gleixner wrote:
> Yijing,
>
> On Thu, 23 Jan 2014, David Laight wrote:
>
>> From: Linuxppc-dev Tony Prisk
>>> On 23/01/14 20:12, Yijing Wang wrote:
>>>> Currently, clocksource_register() and __clocksource_register_scale()
>>>> functions always return 0, it's pointless, make functions void.
>>>> And remove the dead code that check the clocksource_register_hz()
>>>> return value.
>>> ......
>>>> -static inline int clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> +static inline void clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> {
>>>> return __clocksource_register_scale(cs, 1, hz);
>>>> }
>>>
>>> This doesn't make sense - you are still returning a value on a function
>>> declared void, and the return is now from a function that doesn't return
>>> anything either ?!?!
>>> Doesn't this throw a compile-time warning??
>>
>> It depends on the compiler.
>> Recent gcc allow it.
>> I don't know if it is actually valid C though.
>>
>> There is no excuse for it on lines like the above though.
>
> Can you please resend with that fixed against 3.14-rc1 ?
OK, I will resend later.
Thanks!
Yijing.
>
> .
>
--
Thanks!
Yijing
WARNING: multiple messages have this Message-ID (diff)
From: Yijing Wang <wangyijing@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>,
David Laight <David.Laight@ACULAB.COM>
Cc: "'Tony Prisk'" <linux@prisktech.co.nz>,
John Stultz <john.stultz@linaro.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
"linux@lists.openrisc.net" <linux@openrisc.net>,
Sekhar Nori <nsekhar@ti.com>, Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Daniel Walker <dwalker@fifo99.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
"Jonas Bonn" <jonas@southpole.se>,
Kukjin Kim <kgene.kim@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Richard Weinberger <richard@nod.at>,
"x86@kernel.org" <x86@kernel.org>,
Tony Lindgren <tony@atomide.com>,
"Ingo Molnar" <mingo@redhat.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
David Brown <davidb@codeaurora.org>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jeff Dike <jdike@addtoit.com>, Barry Song <baohua@kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"user-mode-linux-user@lists.sourceforge.net"
<user-mode-linux-user@lists.sourceforge.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
Michal Simek <monstr@monstr.eu>,
Jim Cromie <jim.cromie@gmail.com>,
"microblaze-uclinux@itee.uq.edu.au"
<microblaze-uclinux@itee.uq.edu.au>,
Hanjun Guo <guohanjun@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
"Bryan Huntsman" <bryanh@codeaurora.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] clocksource: Make clocksource register functions void
Date: Mon, 10 Feb 2014 09:13:55 +0800 [thread overview]
Message-ID: <52F827D3.5080906@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402052139560.24986@ionos.tec.linutronix.de>
On 2014/2/6 4:40, Thomas Gleixner wrote:
> Yijing,
>
> On Thu, 23 Jan 2014, David Laight wrote:
>
>> From: Linuxppc-dev Tony Prisk
>>> On 23/01/14 20:12, Yijing Wang wrote:
>>>> Currently, clocksource_register() and __clocksource_register_scale()
>>>> functions always return 0, it's pointless, make functions void.
>>>> And remove the dead code that check the clocksource_register_hz()
>>>> return value.
>>> ......
>>>> -static inline int clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> +static inline void clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> {
>>>> return __clocksource_register_scale(cs, 1, hz);
>>>> }
>>>
>>> This doesn't make sense - you are still returning a value on a function
>>> declared void, and the return is now from a function that doesn't return
>>> anything either ?!?!
>>> Doesn't this throw a compile-time warning??
>>
>> It depends on the compiler.
>> Recent gcc allow it.
>> I don't know if it is actually valid C though.
>>
>> There is no excuse for it on lines like the above though.
>
> Can you please resend with that fixed against 3.14-rc1 ?
OK, I will resend later.
Thanks!
Yijing.
>
> .
>
--
Thanks!
Yijing
WARNING: multiple messages have this Message-ID (diff)
From: Yijing Wang <wangyijing@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>,
David Laight <David.Laight@ACULAB.COM>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"x86@kernel.org" <x86@kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
"linux@lists.openrisc.net" <linux@openrisc.net>,
Hanjun Guo <guohanjun@huawei.com>, Sekhar Nori <nsekhar@ti.com>,
Michal Simek <monstr@monstr.eu>,
Paul Mackerras <paulus@samba.org>,
Ralf Baechle <ralf@linux-mips.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Daniel Walker <dwalker@fifo99.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Jonas Bonn <jonas@southpole.se>,
Kukjin Kim <kgene.kim@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Richard Weinberger <richard@nod.at>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Tony Lindgren <tony@atomide.com>, Ingo Molnar <mingo@redhat.com>,
"microblaze-uclinux@itee.uq.edu.au"
<microblaze-uclinux@itee.uq.edu.au>,
David Brown <davidb@codeaurora.org>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Jeff Dike <jdike@addtoit.com>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
"user-mode-linux-user@lists.sourceforge.net"
<user-mode-linux-user@lists.sourceforge.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Barry Song <baohua@kernel.org>, Jim Cromie <jim.cromie@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] clocksource: Make clocksource register functions void
Date: Mon, 10 Feb 2014 09:13:55 +0800 [thread overview]
Message-ID: <52F827D3.5080906@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402052139560.24986@ionos.tec.linutronix.de>
On 2014/2/6 4:40, Thomas Gleixner wrote:
> Yijing,
>
> On Thu, 23 Jan 2014, David Laight wrote:
>
>> From: Linuxppc-dev Tony Prisk
>>> On 23/01/14 20:12, Yijing Wang wrote:
>>>> Currently, clocksource_register() and __clocksource_register_scale()
>>>> functions always return 0, it's pointless, make functions void.
>>>> And remove the dead code that check the clocksource_register_hz()
>>>> return value.
>>> ......
>>>> -static inline int clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> +static inline void clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> {
>>>> return __clocksource_register_scale(cs, 1, hz);
>>>> }
>>>
>>> This doesn't make sense - you are still returning a value on a function
>>> declared void, and the return is now from a function that doesn't return
>>> anything either ?!?!
>>> Doesn't this throw a compile-time warning??
>>
>> It depends on the compiler.
>> Recent gcc allow it.
>> I don't know if it is actually valid C though.
>>
>> There is no excuse for it on lines like the above though.
>
> Can you please resend with that fixed against 3.14-rc1 ?
OK, I will resend later.
Thanks!
Yijing.
>
> .
>
--
Thanks!
Yijing
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Yijing Wang <wangyijing@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>,
David Laight <David.Laight@ACULAB.COM>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"x86@kernel.org" <x86@kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
"linux@lists.openrisc.net" <linux@openrisc.net>,
Hanjun Guo <guohanjun@huawei.com>, Sekhar Nori <nsekhar@ti.com>,
Michal Simek <monstr@monstr.eu>,
Paul Mackerras <paulus@samba.org>,
Ralf Baechle <ralf@linux-mips.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Daniel Walker <dwalker@fifo99.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Jonas Bonn <jonas@southpole.se>,
Kukjin Kim <kgene.kim@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Richard Weinberger <richard@nod.at>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Tony Lindgren <tony@atomide.com>, Ingo Molnar <mingo@redhat.com>,
"microblaze-uclinux@itee.uq.edu.au"
<microblaze-uclinux@itee.uq.edu.au>,
David Brown <davidb@codeaurora.org>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Jeff Dike <jdike@addtoit.com>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
"user-mode-linux-user@lists.sourceforge.net"
<user-mode-linux-user@lists.sourceforge.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Barry Song <baohua@kernel.org>, Jim Cromie <jim.cromie@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
'Tony Prisk' <linux@prisktech.co.nz>,
Bryan Huntsman <bryanh@codeaurora.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] clocksource: Make clocksource register functions void
Date: Mon, 10 Feb 2014 09:13:55 +0800 [thread overview]
Message-ID: <52F827D3.5080906@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402052139560.24986@ionos.tec.linutronix.de>
On 2014/2/6 4:40, Thomas Gleixner wrote:
> Yijing,
>
> On Thu, 23 Jan 2014, David Laight wrote:
>
>> From: Linuxppc-dev Tony Prisk
>>> On 23/01/14 20:12, Yijing Wang wrote:
>>>> Currently, clocksource_register() and __clocksource_register_scale()
>>>> functions always return 0, it's pointless, make functions void.
>>>> And remove the dead code that check the clocksource_register_hz()
>>>> return value.
>>> ......
>>>> -static inline int clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> +static inline void clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> {
>>>> return __clocksource_register_scale(cs, 1, hz);
>>>> }
>>>
>>> This doesn't make sense - you are still returning a value on a function
>>> declared void, and the return is now from a function that doesn't return
>>> anything either ?!?!
>>> Doesn't this throw a compile-time warning??
>>
>> It depends on the compiler.
>> Recent gcc allow it.
>> I don't know if it is actually valid C though.
>>
>> There is no excuse for it on lines like the above though.
>
> Can you please resend with that fixed against 3.14-rc1 ?
OK, I will resend later.
Thanks!
Yijing.
>
> .
>
--
Thanks!
Yijing
WARNING: multiple messages have this Message-ID (diff)
From: wangyijing@huawei.com (Yijing Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] clocksource: Make clocksource register functions void
Date: Mon, 10 Feb 2014 09:13:55 +0800 [thread overview]
Message-ID: <52F827D3.5080906@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402052139560.24986@ionos.tec.linutronix.de>
On 2014/2/6 4:40, Thomas Gleixner wrote:
> Yijing,
>
> On Thu, 23 Jan 2014, David Laight wrote:
>
>> From: Linuxppc-dev Tony Prisk
>>> On 23/01/14 20:12, Yijing Wang wrote:
>>>> Currently, clocksource_register() and __clocksource_register_scale()
>>>> functions always return 0, it's pointless, make functions void.
>>>> And remove the dead code that check the clocksource_register_hz()
>>>> return value.
>>> ......
>>>> -static inline int clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> +static inline void clocksource_register_hz(struct clocksource *cs, u32 hz)
>>>> {
>>>> return __clocksource_register_scale(cs, 1, hz);
>>>> }
>>>
>>> This doesn't make sense - you are still returning a value on a function
>>> declared void, and the return is now from a function that doesn't return
>>> anything either ?!?!
>>> Doesn't this throw a compile-time warning??
>>
>> It depends on the compiler.
>> Recent gcc allow it.
>> I don't know if it is actually valid C though.
>>
>> There is no excuse for it on lines like the above though.
>
> Can you please resend with that fixed against 3.14-rc1 ?
OK, I will resend later.
Thanks!
Yijing.
>
> .
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2014-02-10 1:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 7:12 [PATCH 2/2] clocksource: Make clocksource register functions void Yijing Wang
2014-01-23 7:12 ` Yijing Wang
2014-01-23 7:12 ` Yijing Wang
2014-01-23 7:12 ` Yijing Wang
2014-01-23 7:12 ` Yijing Wang
2014-01-23 7:12 ` Yijing Wang
2014-01-23 7:40 ` Hans-Christian Egtvedt
2014-01-23 7:40 ` Hans-Christian Egtvedt
2014-01-23 7:40 ` Hans-Christian Egtvedt
2014-01-23 7:40 ` Hans-Christian Egtvedt
2014-01-23 7:40 ` Hans-Christian Egtvedt
2014-01-23 7:45 ` Tony Prisk
2014-01-23 7:45 ` Tony Prisk
2014-01-23 7:45 ` Tony Prisk
2014-01-23 7:45 ` Tony Prisk
2014-01-23 7:45 ` Tony Prisk
2014-01-23 7:58 ` Geert Uytterhoeven
2014-01-23 7:58 ` Geert Uytterhoeven
2014-01-23 7:58 ` Geert Uytterhoeven
2014-01-23 7:58 ` Geert Uytterhoeven
2014-01-23 8:04 ` Tony Prisk
2014-01-23 8:04 ` Tony Prisk
2014-01-23 8:04 ` Tony Prisk
2014-01-23 8:04 ` Tony Prisk
2014-01-23 8:17 ` Yijing Wang
2014-01-23 8:17 ` Yijing Wang
2014-01-23 8:17 ` Yijing Wang
2014-01-23 8:17 ` Yijing Wang
2014-01-23 8:17 ` Yijing Wang
2014-01-23 11:40 ` David Laight
2014-01-23 11:40 ` David Laight
2014-01-23 11:40 ` David Laight
2014-01-23 11:40 ` David Laight
2014-01-23 11:40 ` David Laight
2014-02-05 20:40 ` Thomas Gleixner
2014-02-05 20:40 ` Thomas Gleixner
2014-02-05 20:40 ` Thomas Gleixner
2014-02-05 20:40 ` Thomas Gleixner
2014-02-05 20:40 ` Thomas Gleixner
2014-02-10 1:13 ` Yijing Wang [this message]
2014-02-10 1:13 ` Yijing Wang
2014-02-10 1:13 ` Yijing Wang
2014-02-10 1:13 ` Yijing Wang
2014-02-10 1:13 ` Yijing Wang
2014-01-23 8:40 ` Daniel Lezcano
2014-01-23 8:40 ` Daniel Lezcano
2014-01-23 8:40 ` Daniel Lezcano
2014-01-23 8:40 ` Daniel Lezcano
2014-01-23 8:40 ` Daniel Lezcano
[not found] ` <52E0D575.5050702-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-01-23 9:01 ` Yijing Wang
2014-01-23 9:01 ` Yijing Wang
2014-01-23 9:01 ` Yijing Wang
2014-01-23 9:01 ` Yijing Wang
2014-01-23 9:01 ` Yijing Wang
2014-01-23 9:01 ` Yijing Wang
2014-02-05 20:39 ` Thomas Gleixner
2014-02-05 20:39 ` Thomas Gleixner
2014-02-05 20:39 ` Thomas Gleixner
2014-02-05 20:39 ` Thomas Gleixner
2014-02-05 20:39 ` Thomas Gleixner
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=52F827D3.5080906@huawei.com \
--to=wangyijing@huawei.com \
--cc=David.Laight@ACULAB.COM \
--cc=daniel.lezcano@linaro.org \
--cc=dwalker@fifo99.com \
--cc=egtvedt@samfundet.no \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=jonas@southpole.se \
--cc=kgene.kim@samsung.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-msm@v \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@openrisc.net \
--cc=linux@prisktech.co.nz \
--cc=mingo@redhat.com \
--cc=nsekhar@ti.com \
--cc=paulus@samba.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=x86@kernel.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.