From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: Include arch specific gpio.h
Date: Fri, 13 Jul 2012 07:43:29 +0200 [thread overview]
Message-ID: <4FFFB581.5080806@monstr.eu> (raw)
In-Reply-To: <CANr=Z=Yw_XxwNDzit4cZ-o6tW1nWJVgiroEMtUP-Vh03hTuG2Q@mail.gmail.com>
Hi Joe,
<snip>
>>>
>>>
>>> This is generic gpio cleanup but I don't think this is the same thing.
>>> I think you should get some warnings for fdtdec compilation around
>>> missing gpio_request
>>> declaration or you include gpio.h in any other header file which is in
>>> fdtdec.c/h.
>>>
>>>
>>> Sorry I don't really understand that. For me fdtdec.c has #include
>>> <asm-generic/gpio.h> and that is enough to get gpio_request(). Can you
>>> please advise what warning you see and for what board?
>>
>>
>> Microblaze:
>> lib/libgeneric.o: In function `fdtdec_setup_gpio':
>> /mnt/projects/u-boot/lib/fdtdec.c:477: undefined reference to `gpio_request'
>>
>> The same error will be for nios2, openrisc and blackfin because they define
>> gpio_request as static inline function in arch/<arch>/include/asm/gpio.h
>>
>> Because I think there should be asm/gpio.h included which can include
>> asm-generic/gpio.h
>> (this is arm case).
>
> When you send an updated patch you need to add V2 or whatever to the
> subject and you need to include a change log here.
>
> I think you meant to reject this, not the other one here:
> http://patchwork.ozlabs.org/patch/170457
I have sent this patch
http://lists.denx.de/pipermail/u-boot/2012-July/128257.html
which has broken subject that's why I have sent this message (it took me 2-3 mins)
http://lists.denx.de/pipermail/u-boot/2012-July/128259.html
And also send correct patch with proper subject and changelog
http://lists.denx.de/pipermail/u-boot/2012-July/128258.html
http://patchwork.ozlabs.org/patch/170458/
Can you please clarify what's wrong?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2012-07-13 5:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 9:56 [U-Boot] [PATCH] fdt: Include arch specific gpio.h Michal Simek
2012-07-10 21:13 ` Simon Glass
2012-07-11 8:19 ` Michal Simek
2012-07-11 9:59 ` Simon Glass
2012-07-11 10:43 ` Michal Simek
2012-07-11 10:59 ` Simon Glass
2012-07-11 11:21 ` Michal Simek
2012-07-11 12:00 ` Simon Glass
2012-07-11 12:21 ` Michal Simek
2012-07-11 21:02 ` Joe Hershberger
2012-07-12 5:05 ` Simon Glass
2012-07-12 5:33 ` Michal Simek
2012-07-12 5:38 ` Simon Glass
2012-07-12 16:37 ` Joe Hershberger
2012-07-13 5:43 ` Michal Simek [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-29 7:28 Michal Simek
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=4FFFB581.5080806@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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