From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: keir@xen.org, Ian Campbell <Ian.Campbell@citrix.com>,
Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>,
ian.jackson@citrix.com
Subject: Re: [PATCH v4 1/1] Support Odroid-XU board (Exynos 5410)
Date: Wed, 03 Sep 2014 15:15:43 -0400 [thread overview]
Message-ID: <540768DF.8070305@linaro.org> (raw)
In-Reply-To: <CANoR_OBZCWiFhXA9CEqPgtFOCx2Ad9iMgewfvhQjBTyQ0AWqbQ@mail.gmail.com>
On 03/09/14 15:07, Suriyan Ramasami wrote:
> The .compatible is exynos5410_dt_compat which lists
> "samsung,exynos5410". Hence, I wanted to make the whole PLATFORM
> platform specific to the exynos5410.
> Now, rethinking what you have said, I believe as all of this is
> generic code, the .compatible should then be exynos5_dt_compat, thus:
> PLATFORM_START(exynos5, "SAMSUNG EXYNOS5")
> .compatible = exynos5_dt_compat,
> and not, .compatible = exynos5410_dt_compat as it is now.
>
> I believe this is what you were suggesting? In which case when more
> SoCs are added, we just add the corresponding string in
> exynos5_dt_compat. Would that be the correct interpretation?
Yes.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-09-03 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 23:19 [PATCH v4 1/1] Support Odroid-XU board (Exynos 5410) Suriyan Ramasami
2014-08-21 22:21 ` Ian Campbell
2014-08-25 21:45 ` Suriyan Ramasami
2014-08-25 22:06 ` Suriyan Ramasami
2014-08-26 17:34 ` Ian Campbell
2014-08-26 21:01 ` Ian Campbell
2014-08-27 19:27 ` Suriyan Ramasami
2014-09-03 10:03 ` Ian Campbell
2014-09-03 17:55 ` Suriyan Ramasami
2014-09-03 18:25 ` Julien Grall
2014-09-03 19:07 ` Suriyan Ramasami
2014-09-03 19:15 ` Julien Grall [this message]
[not found] ` <1409821081.15505.44.camel@kazak.uk.xensource.com>
2014-09-04 15:44 ` Suriyan Ramasami
2014-09-04 15:51 ` Ian Campbell
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=540768DF.8070305@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).