From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: sparclinux@vger.kernel.org, sfr@canb.auug.org.au,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] sparc/of: Move of_device fields into struct pdev_archdata
Date: Wed, 16 Jun 2010 14:06:38 -0700 (PDT) [thread overview]
Message-ID: <20100616.140638.115932212.davem@davemloft.net> (raw)
In-Reply-To: <20100604211132.2762.54164.stgit@angua>
From: Grant Likely <grant.likely@secretlab.ca>
Date: Fri, 04 Jun 2010 15:11:33 -0600
> This patch moves SPARC architecture specific data members out of
> struct of_device and into the pdev_archdata structure. The reason
> for this change is to unify the struct of_device definition amongst
> all the architectures. It also remvoes the .sysdata, .slot, .portid
> and .clock_freq properties because they aren't actually used by
> anything.
>
> A subsequent patch will replace struct of_device entirely with struct
> platform_device and the of_platform support code will share common
> routines with the platform bus (but the bus instances themselves can
> remain separate).
>
> This patch also adds 'struct resources *resource' and num_resources
> to match the fields defined in struct platform_device. After this
> change, 'struct platform_device' can be used as a drop-in replacement
> for 'struct of_platform'.
>
> This change is in preparation for merging the of_platform_bus_type
> with the platform_bus_type.
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2010-06-16 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100604205930.2762.17131.stgit@angua>
2010-06-04 21:11 ` [PATCH 1/2] sparc/of: Move of_device fields into struct pdev_archdata Grant Likely
2010-06-16 21:06 ` David Miller [this message]
2010-06-04 21:11 ` [PATCH 2/2] of: kill struct of_device Grant Likely
2010-06-16 21:07 ` 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=20100616.140638.115932212.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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