From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: Michal Simek <monstr@monstr.eu>,
microblaze-uclinux@itee.uq.edu.au,
devicetree-discuss@lists.ozlabs.org,
Paul Mackerras <paulus@samba.org>,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
David Miller <davem@davemloft.net>
Subject: Re: Using devices trees on X86
Date: Tue, 29 Jun 2010 12:38:43 +1000 [thread overview]
Message-ID: <20100629123843.5f94d477.sfr@canb.auug.org.au> (raw)
In-Reply-To: <0bcc23b9-2cbd-4465-b17c-7b3c2dff9fd3@VA3EHSMHS007.ehs.local>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
Hi Stephen,
On Mon, 28 Jun 2010 10:57:33 -0700 Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
>
> 2) config OF is currently implemented in the architecture code. This
> should be non-architecture dependent and selected by the arches that
> need it.
>
> Comments greatly appreciated, in particular if you have
> likely-to-be-easy-to-get-accepted suggestions for 3), or feel like
> carefully solving 2) in
> a way which doesn't bork the existing of-based arches.
See the following patch set. Parts 1, 2 and 3 could be applied to the
respective architecture trees as well as Grant's tree to aleviate some
conflict problems. Part 5 could wait until a later time if necessary.
However, this is relatively trivial, so we could just collect ACKs and
put it all in Grant's tree and live with any minor pain.
Having OF in more than one Kconfig file should not cause any problems as
long as they are all the same.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next parent reply other threads:[~2010-06-29 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0bcc23b9-2cbd-4465-b17c-7b3c2dff9fd3@VA3EHSMHS007.ehs.local>
2010-06-29 2:38 ` Stephen Rothwell [this message]
2010-06-29 2:42 ` [PATCH 1/5] microblaze: turn CONFIG_OF into a select Stephen Rothwell
2010-06-29 9:57 ` Michal Simek
2010-06-29 2:43 ` [PATCH 2/5] powerpc: " Stephen Rothwell
2010-06-29 2:44 ` [PATCH 3/5] sparc: " Stephen Rothwell
2010-06-29 3:11 ` David Miller
2010-06-29 2:45 ` [PATCH 4/5] of: define CONFIG_OF globally so architectures can select it Stephen Rothwell
2010-06-29 2:47 ` [PATCH 5/5] of: remove architecture CONFIG_OF definitions Stephen Rothwell
2010-06-29 9:58 ` Michal Simek
2010-06-29 5:56 ` Using devices trees on X86 Grant Likely
2010-06-29 6:02 ` Stephen Rothwell
2010-06-29 15:56 ` Stephen Neuendorffer
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=20100629123843.5f94d477.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
--cc=paulus@samba.org \
--cc=sparclinux@vger.kernel.org \
--cc=stephen.neuendorffer@xilinx.com \
/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).