From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ti-gfx: build with GCC 4.8
Date: Wed, 26 Feb 2014 23:19:57 +0100 [thread overview]
Message-ID: <20140226221957.GC16780@free.fr> (raw)
In-Reply-To: <1392391790-22941-1-git-send-email-syntheticpp@gmx.net>
Peter, All,
On 2014-02-14 16:29 +0100, Peter K?mmel spake thusly:
> In older kernels clk_disable() is a void function.
Not only in older kernels, but in recent kernels, too.
For example, in v3.14-rc4:
$ git grep 'void clk_disable' include
include/linux/clk.h:void clk_disable(struct clk *clk);
> Signed-off-by: Peter K?mmel <syntheticpp@gmx.net>
> ---
> package/ti-gfx/ti-gfx-newclkapi.patch | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/ti-gfx/ti-gfx-newclkapi.patch b/package/ti-gfx/ti-gfx-newclkapi.patch
> index 8f50c7e..29ad20d 100644
> --- a/package/ti-gfx/ti-gfx-newclkapi.patch
> +++ b/package/ti-gfx/ti-gfx-newclkapi.patch
> @@ -14,7 +14,7 @@ Index: ti-gfx-4_09_00_01/GFX_Linux_KM/services4/system/omap3630/sysutils_linux.c
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(3,2,0)
> +int clk_disable_unprepare(struct clk *clk)
> +{
> -+ return clk_disable(clk);
> ++ clk_disable(clk); return 0;
> +}
> +#elif LINUX_VERSION_CODE < KERNEL_VERSION(3,3,0)
> +int clk_disable_unprepare(struct clk *clk)
> @@ -35,7 +35,7 @@ Index: ti-gfx-4_09_00_01/GFX_Linux_KM/services4/system/omap3630/sysutils_linux.c
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(3,2,0)
> +int clk_prepare_enable(struct clk *clk)
> +{
> -+ return clk_enable(clk);
> ++ clk_enable(clk); return 0;
But why did you change clk_enable too? As far as I can see, it always
returned an int, for as long as it existed. Eg. in v2.6.19:
$ git grep 'int clk_enable' include
include/linux/clk.h:int clk_enable(struct clk *clk);
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-02-26 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 15:29 [Buildroot] [PATCH 1/1] ti-gfx: build with GCC 4.8 Peter Kümmel
2014-02-26 22:19 ` Yann E. MORIN [this message]
2014-02-27 6:14 ` Peter Kümmel
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=20140226221957.GC16780@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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