public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: microblaze-linux@lists.itee.uq.edu.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] microblaze: Do not select GENERIC_GPIO by default
Date: Thu, 12 Apr 2012 09:46:46 +0200	[thread overview]
Message-ID: <4F868866.6020206@monstr.eu> (raw)
In-Reply-To: <4F842CB8.4070900@metafoo.de>

On 04/10/2012 02:51 PM, Lars-Peter Clausen wrote:
> On 04/10/2012 02:37 PM, Michal Simek wrote:
>> Hi Lars,
>>
>> 2012/4/9 Lars-Peter Clausen<lars@metafoo.de<mailto:lars@metafoo.de>>
>>
>>      The microblaze architecture does not provide a native GPIO API
>>      implementation
>>      nor requires GPIOLIB, but still selects GENERIC_GPIO by default. As a
>>      result the
>>      following build error occurs, if GPIOLIB is not selected:
>>
>>             include/asm-generic/gpio.h: In function 'gpio_get_value_cansleep':
>>             include/asm-generic/gpio.h:218: error: implicit declaration of
>>      function '__gpio_get_value'
>>             include/asm-generic/gpio.h: In function 'gpio_set_value_cansleep':
>>             include/asm-generic/gpio.h:224: error: implicit declaration of
>>      function '__gpio_set_value'
>>
>>      This patch addresses the issue by not selecting GENERIC_GPIO by default.
>>      This
>>      causes the GPIO API to be stubbed out if no implementation is provided.
>>
>>      Signed-off-by: Lars-Peter Clausen<lars@metafoo.de<mailto:lars@metafoo.de>>
>>      Cc: stable@vger.kernel.org<mailto:stable@vger.kernel.org>
>>      ---
>>       arch/microblaze/Kconfig |    2 +-
>>       1 file changed, 1 insertion(+), 1 deletion(-)
>>
>>
>> Sorry for taking so long. Can you please send me your .config file. I have
>> never seen that Microblaze has any problem with it.
>>
>
> Hi,
>
> basically any config which has CONFIG_GPIOLIB not set. I've attached my config.

Will add it to mainline.

Tested-by: Michal Simek <monstr@monstr.eu>

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

  reply	other threads:[~2012-04-12  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 13:05 [PATCH resend] microblaze: Do not select GENERIC_GPIO by default Lars-Peter Clausen
     [not found] ` <CAHTX3dK4vzjtW+vvS5pokqrvmdbGYdj=TR3jwfkWW9xCk1QiXQ@mail.gmail.com>
2012-04-10 12:51   ` Lars-Peter Clausen
2012-04-12  7:46     ` Michal Simek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-08 10:05 Lars-Peter Clausen

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=4F868866.6020206@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-linux@lists.itee.uq.edu.au \
    /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