From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Use <linux/of_{platform, device}.h> and not <asm/...> variants.
Date: Wed, 9 Jan 2008 10:29:12 +1100 [thread overview]
Message-ID: <20080109102912.16215a01.sfr@canb.auug.org.au> (raw)
In-Reply-To: <E1JCF5S-00043W-0U@jdl.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
On Tue, 08 Jan 2008 08:05:49 -0600 Jon Loeliger <jdl@jdl.com> wrote:
>
> By $DIETY, I'll obtain Janitorial Karma one way or another!
:-)
> The question now is, what next? I'm thinking about
> picking on arch/sparc/, then drivers/ and sound/,
> and finally pick off /include.
arch/sparc{,64} should be easy if you have a cross compiler (though it
should work, Dave gets cranky if you break his tree :-)) Dave should just
take the patches if you do test compile them. Tell him I sent you :-)
> To be honest, I'm not sure what the final /include
> structure is supposed to look like or do as both
> pairs of these files mutually include their counterpart.
> (i/l/of_d.h includes i/a/of_d.h which includes i/l/of_d.h)
> (i/l/of_p.h includes i/a/of_p.h which includes i/l/of_p.h)
The intention is that everyone only includes linux/of*.h (except for
linux/of*.h of course) at which point we should be able to remove the
includes of linux/of*.h from asm*/of*.h.
> But, of course, the various asm/of_{platform,device}.h files
> are different for each arch/, so I wasn't sure if the longer
> term plan had folding the arch variants straight into the
> include/linux/ version of the file or not. Seems there will
> come a point when the sparc and powerpc variants will need
> to be more unified...
Some more unification should be possible over time, but that is much
harder.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-08 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 18:07 [PATCH] Use <linux/of_{platform, device}.h> and not <asm/...> variants Jon Loeliger
2008-01-08 0:36 ` Stephen Rothwell
2008-01-08 14:05 ` Jon Loeliger
2008-01-08 23:29 ` Stephen Rothwell [this message]
2008-01-09 0:45 ` [PATCH] Use <linux/of_{platform, device}.h> and not <asm/...>variants 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=20080109102912.16215a01.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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).