From: Chen Gang <gang.chen@asianux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Arnd Bergmann <arnd@arndb.de>,
"dhowells@redhat.com" <dhowells@redhat.com>,
Dave Jones <davej@redhat.com>, David Sharp <dhsharp@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] h8300: include: asm: Kbuild: add gpio.h for pass compiling
Date: Fri, 30 Aug 2013 17:12:34 +0800 [thread overview]
Message-ID: <52206202.8050001@asianux.com> (raw)
In-Reply-To: <521C26FA.8050208@asianux.com>
On 08/27/2013 12:11 PM, Chen Gang wrote:
> On 08/26/2013 06:59 PM, Chen Gang wrote:
>> On 08/26/2013 06:21 PM, Geert Uytterhoeven wrote:
>>> On Mon, Aug 26, 2013 at 12:16 PM, Chen Gang <gang.chen@asianux.com> wrote:
>>>> Need add default "gpio.h" for h8300, or can not pass compiling.
>>>>
>>>> The related error (allmodconfig for h8300):
>>>>
>>>> arch/h8300/kernel/h8300_ksyms.c:17:22: fatal error: asm/gpio.h: No such file or directory
>>>> #include <asm/gpio.h>
>>>> ^
>>>
>>> I this include needed at all? Perhaps it can just be removed?
>>>
>>
>> Pardon ? Do you mean, only removing it will be OK ?
>>
>>>> Signed-off-by: Chen Gang <gang.chen@asianux.com>
>>>> ---
>>>> arch/h8300/include/asm/Kbuild | 1 +
>>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/arch/h8300/include/asm/Kbuild b/arch/h8300/include/asm/Kbuild
>>>> index 8ada3cf..4c627aa 100644
>>>> --- a/arch/h8300/include/asm/Kbuild
>>>> +++ b/arch/h8300/include/asm/Kbuild
>>>> @@ -1,6 +1,7 @@
>>>>
>>>> generic-y += clkdev.h
>>>> generic-y += exec.h
>>>> +generic-y += gpio.h
>>>> generic-y += linkage.h
>>>> generic-y += mmu.h
>>>> generic-y += module.h
>>>
>>> The only gpio-related exports in arch/h8300/kernel/h8300_ksyms.c are:
>>>
>>> EXPORT_SYMBOL(h8300_reserved_gpio);
>>> EXPORT_SYMBOL(h8300_free_gpio);
>>> EXPORT_SYMBOL(h8300_set_gpio_dir);
>>>
>>> and these are definitely not provided by asm-generic/gpio.h.
>>>
>>
>> Yeah, I will try to remove "#include <asm/gpio.h>" to see whether can
>> pass compiling, tomorrow. :-)
>>
>> And now, I feel (just guess), it will not, for h8300 really need gpio
>> (it has "gpio-internal.h"), commonly it will need "asm/gpio.h" too.
>>
>> Tomorrow, I will try to prove whether my guess is correct or not. ;-).
>>
>
> After reading the related code (search "gpio.h" in root source tree),
> it seems what you said is correct, my guess is incorrect. :-(
>
> Hmm... but better to get final conclusion after finish allmodconfig
> compiling.
>
> Now, I am compiling, and excuse me, I can not finish today because of
> some issues (mainly for 'gcc 4.8.0', part for 'ld 2.22', and part for
> kernel), I will 'process' them, hope can finish before 2013-08-31.
>
Oh, sorry, I can not finish allmodconfig today, I have to delay the
schedule.
The excuse is "it is too many issues (both for h8000 and for other sub
systems) than I guessed originally".
I should try to finish it within next week (2013-09-06).
BTW: I disable the '-Os' for allmodconfig under h8300, or gcc will cause
many various bugs (disable '-Os' doesn't matter with our goal, and I
will continue for gcc issues with gcc guys, next).
Thanks.
>
> Welcome additional suggestions or completions.
>
> Thanks.
>
>>
>> Thanks.
>>
>>> Gr{oetje,eeting}s,
>>>
>>> Geert
>>>
>>> --
>>> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>>>
>>> In personal conversations with technical people, I call myself a hacker. But
>>> when I'm talking to journalists I just say "programmer" or something like that.
>>> -- Linus Torvalds
>>>
>>>
>>
>>
>
>
--
Chen Gang
prev parent reply other threads:[~2013-08-30 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 10:16 [PATCH] h8300: include: asm: Kbuild: add gpio.h for pass compiling Chen Gang
2013-08-26 10:21 ` Geert Uytterhoeven
2013-08-26 10:59 ` Chen Gang
2013-08-27 4:11 ` Chen Gang
2013-08-30 9:12 ` Chen Gang [this message]
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=52206202.8050001@asianux.com \
--to=gang.chen@asianux.com \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=dhsharp@google.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=ysato@users.sourceforge.jp \
/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.