From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
sergei.shtylyov@cogentembedded.com,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
devicetree@vger.kernel.org, Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/3] of: add vendor prefix for Mentor Graphics
Date: Mon, 19 Aug 2013 19:14:25 +0200 [thread overview]
Message-ID: <52125271.404@linutronix.de> (raw)
In-Reply-To: <52123EAA.10507@wwwdotorg.org>
On 08/19/2013 05:50 PM, Stephen Warren wrote:
>>>> arch/arm/boot/dts/am33xx.dtsi:375: compatible = "mg,musbmhdrc";
>>>> arch/arm/boot/dts/am33xx.dtsi:430: compatible = "mg,musbmhdrc";
>>>
>>>> arch/arm/boot/dts/dbx5x0.dtsi:181: "mentor,musb";
>>>
>>> Should both be documented? Should the bindings for those devices be
>>> unified on one vendor prefix, with the old one perhaps still documented
>>> as deprecated depending on how long it's been around?
>>
>> I wasn't aware of the dbx5x0 mentor,usb binding. As far as the am33xx
>> is concerned, it has been prepared for the next merge window and can be
>> changed.
>
> OK, changing it to mentor, seems simplest and most convenient then.
Okay.
>> However the mentor,usb binding isn't documented either.
>
> Presumably you can just adjust this patch to document it.
Okay. That means if we stick to that hierarchy given my dbx5x0 (which
makes sense after thinking for a while) I'm going to shift my devices a
little to fit this. Once this is done I document it and post patches.
Sebastian
prev parent reply other threads:[~2013-08-19 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376572427-17689-1-git-send-email-bigeasy@linutronix.de>
[not found] ` <520EAD1D.2090802@wwwdotorg.org>
[not found] ` <520F41F0.8080707@linutronix.de>
2013-08-19 15:50 ` [PATCH 1/3] of: add vendor prefix for Mentor Graphics Stephen Warren
2013-08-19 17:14 ` Sebastian Andrzej Siewior [this message]
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=52125271.404@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=lee.jones@linaro.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=swarren@wwwdotorg.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).