From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Russell King <rmk@arm•linux.org.uk>
Cc: Takashi Iwai <tiwai@suse•de>, Marek Vasut <marek.vasut@gmail•com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: arm tree build failure
Date: Wed, 20 Aug 2008 10:01:06 +1000 [thread overview]
Message-ID: <20080820100106.b775b134.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080819160656.GA20537@flint.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi Russell,
On Tue, 19 Aug 2008 17:06:56 +0100 Russell King <rmk@arm•linux.org.uk> wrote:
>
> 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?
Fine by me - that goes for all merge/build fixes I do for linux-next.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-08-20 0:01 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
2008-08-19 16:32 ` Takashi Iwai
2008-08-20 0:01 ` Stephen Rothwell [this message]
-- 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=20080820100106.b775b134.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marek.vasut@gmail$(echo .)com \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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