From: Julien Grall <julien.grall@linaro.org>
To: Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
Chen Baozi <baozich@gmail.com>, Tim Deegan <tim@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v02 3/3] xen/arm: add DRA7 platform definition
Date: Wed, 02 Jul 2014 17:51:06 +0100 [thread overview]
Message-ID: <53B4387A.2020607@linaro.org> (raw)
In-Reply-To: <CAH_mUMMPHtsyWBP5mx6XL2M-zJCD4dZFdzVDDZDZYk-unXmaaw@mail.gmail.com>
On 07/02/2014 05:34 PM, Andrii Tseglytskyi wrote:
> I would like to create two standalone platform definitions and two
> compatible lists. The reason is - common OMAP5 uses specific_mapping
> callback, which is not needed by DRA7. In case if we decide to merge
> platforms - this should be resolved somehow.
> What do you think?
Oops, I didn't notice that you didn't use the specific_mapping callback.
In this case, you will have to create 2 compatible lists.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-07-02 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 13:49 [PATCH v02 0/3] arm: introduce basic DRA7 platform support Andrii Tseglytskyi
2014-07-02 13:49 ` [PATCH v02 1/3] xen/dt: add match for non-available nodes Andrii Tseglytskyi
2014-07-03 9:53 ` Ian Campbell
2014-07-03 10:32 ` Andrii Tseglytskyi
2014-07-03 12:07 ` Ian Campbell
2014-07-02 13:49 ` [PATCH v02 2/3] xen/arm: dra7: Add UART base address for early logging Andrii Tseglytskyi
2014-07-03 9:53 ` Ian Campbell
2014-07-02 13:50 ` [PATCH v02 3/3] xen/arm: add DRA7 platform definition Andrii Tseglytskyi
2014-07-02 14:05 ` Julien Grall
2014-07-02 15:02 ` Andrii Tseglytskyi
2014-07-02 15:18 ` Julien Grall
2014-07-02 16:34 ` Andrii Tseglytskyi
2014-07-02 16:51 ` Julien Grall [this message]
2014-07-02 17:09 ` Andrii Tseglytskyi
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=53B4387A.2020607@linaro.org \
--to=julien.grall@linaro.org \
--cc=andrii.tseglytskyi@globallogic.com \
--cc=baozich@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.