From: Russell King <rmk@arm.linux.org.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Marek Vasut <marek.vasut@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: linux-next: arm tree build failure
Date: Tue, 19 Aug 2008 17:06:56 +0100 [thread overview]
Message-ID: <20080819160656.GA20537@flint.arm.linux.org.uk> (raw)
In-Reply-To: <s5hljytw8qf.wl%tiwai@suse.de>
On Tue, Aug 19, 2008 at 01:21:44PM +0200, Takashi Iwai wrote:
> I also got a build error with ucb1400 regarding undefined
> gpio_get_value() (sorry I lost the exact build log).
>
> The patch below fixes it, but not 100% sure whether it breaks the
> build on ARM. Please check it.
There's nothing in ucb1400.h that would require gpio.h, nor in
ucb1400_*.c, so I think it's safe to remove. Mind if I merge your
patch into Marek's original to avoid bisect problems?
Ditto for Stephen's patch?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-08-19 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 5:53 linux-next: arm tree build failure Stephen Rothwell
2008-08-19 11:16 ` Marek Vasut
2008-08-19 11:21 ` Takashi Iwai
2008-08-19 16:06 ` Russell King [this message]
2008-08-19 16:32 ` Takashi Iwai
2008-08-20 0:01 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 18:09 Stephen Rothwell
2008-09-18 18:26 ` Eric Miao
2008-09-18 18:33 ` Eric Miao
2008-09-18 22:04 ` Russell King
2008-09-18 22:28 ` Eric Miao
2009-02-14 4:27 Stephen Rothwell
2009-02-16 9:23 ` Catalin Marinas
2009-04-14 7:48 Stephen Rothwell
2009-04-14 17:09 ` Russell King
2009-09-10 4:59 Stephen Rothwell
2009-09-14 8:20 ` Russell King
2010-01-28 23:38 Stephen Rothwell
2010-01-29 23:45 ` Russell King
2010-01-30 1:27 ` Stephen Rothwell
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=20080819160656.GA20537@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-next@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.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 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.