From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: "amba: Remove AMBA level regulator support" commit.
Date: Fri, 13 Apr 2012 14:26:04 +0200 [thread overview]
Message-ID: <CACRpkdYkTHcppMtEy94cRiaHApeeohiiaCaA0SuyG52n1s+Yag@mail.gmail.com> (raw)
In-Reply-To: <20120413012230.GA30438@windriver.com>
On Fri, Apr 13, 2012 at 3:22 AM, Paul Gortmaker
<paul.gortmaker@windriver.com> wrote:
> is pointed at by git bisect for the u8500_defconfig build failure:
>
> drivers/dma/ste_dma40.c:2708:3: error: implicit declaration of function
> 'regulator_disable' [-Werror=implicit-function-declaration]
> drivers/dma/ste_dma40.c:2747:3: error: implicit declaration of function
> 'regulator_enable' [-Werror=implicit-function-declaration]
> drivers/dma/ste_dma40.c:3260:3: error: implicit declaration of function
> 'regulator_get' [-Werror=implicit-function-declaration]
> drivers/dma/ste_dma40.c:3271:4: error: implicit declaration of function
> 'regulator_put' [-Werror=implicit-function-declaration]
I've already sent a patch to the DMA maintainer to fix this.
It was a bug in the DMA driver actually - it did not include the proper
headers - so it just got triggered by this patch.
http://marc.info/?l=linux-kernel&m=133424730706377&w=2
Yours,
Linus Walleij
prev parent reply other threads:[~2012-04-13 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 1:22 linux-next: "amba: Remove AMBA level regulator support" commit Paul Gortmaker
2012-04-13 2:01 ` Shawn Guo
2012-04-13 10:32 ` Russell King - ARM Linux
2012-04-13 10:44 ` Mark Brown
2012-04-13 10:49 ` Russell King - ARM Linux
2012-04-13 11:25 ` Mark Brown
2012-04-13 12:17 ` Fabio Estevam
2012-04-13 12:07 ` Mark Brown
2012-04-13 12:19 ` Russell King - ARM Linux
2012-04-13 14:04 ` Mark Brown
2012-04-13 12:30 ` Linus Walleij
2012-04-13 8:37 ` Mark Brown
2012-04-13 12:26 ` Linus Walleij [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=CACRpkdYkTHcppMtEy94cRiaHApeeohiiaCaA0SuyG52n1s+Yag@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).