From: David Miller <davem@davemloft.net>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] Add include of linux/of.h to numa.c
Date: Wed, 13 Feb 2008 16:54:13 -0800 (PST) [thread overview]
Message-ID: <20080213.165413.201539871.davem@davemloft.net> (raw)
In-Reply-To: <3bcbba96837cfcdeb873d26d51241c9659e77930.1202949456.git.michael@ellerman.id.au>
From: Michael Ellerman <michael@ellerman.id.au>
Date: Thu, 14 Feb 2008 11:37:49 +1100 (EST)
> numa.c requires routines in linux/of.h, so should include it.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Thanks for looking into these build failures Michael.
I actually just finished respinning the LMB tree, which
I'll post about next, and I dealt with this asm/prom.h
issue in what I believe should be a more fail-safe way
from the get-go.
Have a look when I post that, and let me know if the build is OK.
Thanks!
prev parent reply other threads:[~2008-02-14 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 0:37 [PATCH 1/2] Add include of linux/of.h to numa.c Michael Ellerman
2008-02-14 0:37 ` [PATCH 2/2] Add include of linux/of.h to os-area.c Michael Ellerman
2008-02-14 0:54 ` David Miller [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=20080213.165413.201539871.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).