From: Haojian Zhuang <haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>
Cc: Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Guennadi Liakhovetski
<g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>
Subject: Re: Device-tree and Marvell vendor prefix
Date: Fri, 20 Jun 2014 08:36:40 +0800 [thread overview]
Message-ID: <CAN1soZztOAJv1TRAt1roOASeU1Lm5C+YiL-+BQ+D_QuyJxmQ0g@mail.gmail.com> (raw)
In-Reply-To: <8738f0so0m.fsf-GANU6spQydw@public.gmane.org>
On Fri, Jun 20, 2014 at 3:22 AM, Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org> wrote:
>
> Hi Haojian, Grant and Rob,
>
> I'm submitting various patches for Marvell PXA27x architecture to support
> device-tree.
>
> In a review from Guennadi, he made me a comment that the official prefix for
> Marvell is "marvell" (according to
> Documentation/devicetree/bindings/vendor-prefixes.txt).
>
> As a matter of fact, there are 2 prefixes used :
> - "marvell" : 264 uses in *.c files
> - "mrvl" : 64 uses in *.c files
>
> So which one should I use ?
>
> Cheers.
>
> --
> Robert
Please use "marvell" instead since it's preferred. We can't replace
"mrvl" by "marvell" roughly.
It may cause incompatible in other's tree. We can add "marvell" for
all "mrvl" entries.
Regards
Haojian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-20 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 19:22 Device-tree and Marvell vendor prefix Robert Jarzmik
[not found] ` <8738f0so0m.fsf-GANU6spQydw@public.gmane.org>
2014-06-20 0:36 ` Haojian Zhuang [this message]
2014-06-20 19:53 ` Jason Cooper
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=CAN1soZztOAJv1TRAt1roOASeU1Lm5C+YiL-+BQ+D_QuyJxmQ0g@mail.gmail.com \
--to=haojian.zhuang-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=g.liakhovetski-Mmb7MZpHnFY@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robert.jarzmik-GANU6spQydw@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).