From: Greg Ungerer <gregungerer@westnet.com.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alex Courbot <acourbot@nvidia.com>,
"Bityutskiy, Artem" <artem.bityutskiy@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-m68k@lists.linux-m68k.org"
<linux-m68k@lists.linux-m68k.org>,
Grant Likely <grant.likely@secretlab.ca>,
Jonas Bonn <jonas@southpole.se>
Subject: Re: m68k build regression
Date: Mon, 08 Apr 2013 17:40:02 +1000 [thread overview]
Message-ID: <51627452.1000908@westnet.com.au> (raw)
In-Reply-To: <CACRpkdapsvstebGqO3H9TkA155xPRb0sb=UEUmf9EJfg5mrpkw@mail.gmail.com>
Hi Linus,
On 08/04/13 17:20, Linus Walleij wrote:
> On Mon, Apr 8, 2013 at 6:32 AM, Greg Ungerer <gregungerer@westnet.com.au> wrote:
>
>> Or we could fix like this, keeping the existing local functions
>> intact for this one last kernel version.
>>
>> Regards
>> Greg
>>
>>
>> [PATCH] m68k: define a local gpio_request_one() function
>>
>> Compiling for linux-3.9-rc1 and later fails with:
>>
>> drivers/gpio/devres.c: In function 'devm_gpio_request_one':
>> drivers/gpio/devres.c:90:2: error: implicit declaration of function 'gpio_request_one' [-Werror=implicit-function-declaration]
>>
>> So provide a local gpio_request_one() function. Code largely borrowed from
>> blackfin's local gpio_request_one() function.
>>
>> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Greg, are you pushing this patch then?
I am happy to push to Linus if everyone is happy with that.
Regards
Greg
prev parent reply other threads:[~2013-04-08 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:39 m68k build regression Bityutskiy, Artem
2013-04-05 14:49 ` Linus Walleij
2013-04-05 17:20 ` Alex Courbot
2013-04-08 4:32 ` Greg Ungerer
2013-04-08 7:20 ` Linus Walleij
2013-04-08 7:40 ` Greg Ungerer [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=51627452.1000908@westnet.com.au \
--to=gregungerer@westnet.com.au \
--cc=acourbot@nvidia.com \
--cc=artem.bityutskiy@intel.com \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=jonas@southpole.se \
--cc=linus.walleij@linaro.org \
--cc=linux-m68k@lists.linux-m68k.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.