From: Michael Ellerman <michael@ellerman.id.au>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4]: Respun LMB patches.
Date: Sat, 16 Feb 2008 06:05:37 +1100 [thread overview]
Message-ID: <1203102337.6699.0.camel@concordia> (raw)
In-Reply-To: <20080213.170938.34536425.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Wed, 2008-02-13 at 17:09 -0800, David Miller wrote:
> I've taken into consideration the various feedback, and
> ported the bug fix and other LMB patches posted recently
> in an effort to keep the patch churn by others down wrt.
> my moving of these files.
>
> 1) Use HAVE_LMB as suggested by Sam.
>
> 2) Fix potential build errors wrt. asm/prom.h dependencies.
>
> My algorithm was:
>
> a) If the file only included asm/lmb.h I added an include
> of both linux/lmb.c and asm/prom.h
>
> b) If the file already includes asm/prom.h, I merely
> changed the asm/lmb.h to linux/lmb.h
That fixes the build failures I was seeing, ack.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-15 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 1:09 [PATCH 0/4]: Respun LMB patches David Miller
2008-02-14 20:58 ` Becky Bruce
2008-02-14 21:24 ` Josh Boyer
2008-02-14 22:15 ` David Miller
2008-02-15 22:12 ` Josh Boyer
2008-02-14 22:13 ` David Miller
2008-02-14 23:21 ` Olof Johansson
2008-02-15 0:58 ` Stephen Rothwell
2008-02-15 19:05 ` Michael Ellerman [this message]
2008-02-15 23:45 ` David Miller
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=1203102337.6699.0.camel@concordia \
--to=michael@ellerman.id.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sparclinux@vger.kernel.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).