From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Rob Herring <robherring2@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, Rob Landley <rob@landley.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Joe Perches <joe@perches.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Documentation: dt: Reduce fragmentation of <..> placeholders
Date: Fri, 11 Apr 2014 11:55:00 +0200 [thread overview]
Message-ID: <5347BBF4.2060408@epfl.ch> (raw)
In-Reply-To: <CAL_JsqLiAF916KvHDgRu2df0qbkYAUL51BFq-62z50xfzZOr-g@mail.gmail.com>
Hi,
On 04/11/2014 02:25 AM, Rob Herring wrote:
> On Sat, Mar 8, 2014 at 3:09 PM, Rob Herring <robherring2@gmail.com> wrote:
>> On Fri, Mar 7, 2014 at 5:28 PM, Florian Vaussard
>> <florian.vaussard@epfl.ch> wrote:
>>> Placeholders <..> are sometimes used in the devicetree documentation
>>> to define family-wide compatible strings (like fsl,<chip>-ipu where
>>> chip can be any Freescale SoC).
>>>
>>> These placeholders are loosly defined. This lead to some
>>> fragmentation. Looking at the current placeholders, we have:
>>>
>>> 3 <board>
>>> 32 <chip>
>>> 1 <chip name>
>>> 1 <mcu-chip>
>>> 1 <processor>
>>> 30 <soc>
>>> 1 <SOC>
>>> 1 <soc-family>
>>>
>>> This patch consolidates this to:
>>>
>>> 3 <board>
>>> 33 <chip>
>>> 1 <mcu-chip>
>>> 1 <processor>
>>> 32 <soc>
>>>
>>
>> I would prefer to consolidate these into just board and chip. If we
>> have any oddballs, they can just document the exact strings.
>
> Florian, Do you plan to re-spin this? I can take it for 3.15 if it is
> early in the rc's.
>
Yes sure, I can re-spin this as soon as 3.15-rc1 is out.
Regards,
Florian
prev parent reply other threads:[~2014-04-11 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 12:36 [PATCH] Documentation: dt: Reduce fragmentation of <..> placeholders Florian Vaussard
2014-03-07 12:57 ` Geert Uytterhoeven
2014-03-07 23:28 ` [PATCH v2] " Florian Vaussard
2014-03-08 21:09 ` Rob Herring
2014-04-11 0:25 ` Rob Herring
2014-04-11 9:55 ` Florian Vaussard [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=5347BBF4.2060408@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
/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).