devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Bresticker <abrestic@chromium.org>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Linux-MIPS <linux-mips@linux-mips.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Arend van Spriel <arend@broadcom.com>
Subject: Re: [PATCH 1/2] MIPS: Move device-trees into vendor sub-directories
Date: Tue, 23 Dec 2014 08:41:23 -0800	[thread overview]
Message-ID: <CAL1qeaH6d5DSU9UgnS4eGvFcAJXEw2iXX8czkCFd8ogdNDLEvQ@mail.gmail.com> (raw)
In-Reply-To: <CAJiQ=7A0ZrNr0+mbHs1xJNDHEJMiG7v69XhEtCyWTYrBtX1zpw@mail.gmail.com>

On Tue, Dec 23, 2014 at 8:20 AM, Kevin Cernekee <cernekee@gmail.com> wrote:
> On Tue, Dec 23, 2014 at 8:07 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> 2014-12-22 15:27 GMT-08:00 Andrew Bresticker <abrestic@chromium.org>:
>>> Move the MIPS device-trees into the appropriate vendor sub-directories.
>>>
>>> Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
>>> ---
>>>  arch/mips/Makefile                                 |  2 +-
>>>  arch/mips/boot/dts/Makefile                        | 33 ++++++++--------------
>>>  arch/mips/boot/dts/bcm/Makefile                    |  9 ++++++
>>>  arch/mips/boot/dts/{ => bcm}/bcm3384.dtsi          |  0
>>>  arch/mips/boot/dts/{ => bcm}/bcm93384wvg.dts       |  0
>>
>> Let's use brcm here, which is the DT vendor prefix, or go full name
>> with broadcom, there has been enough debate in the past about this ;)
>
> IOW we want to see:
>
> arch/mips/boot/dts/brcm/bcm3384.dtsi
> arch/mips/boot/dts/brcm/bcm93384wvg.dts
>
> right?  "brcm" for the vendor name, "bcmXXXX[X[X]]" for the chip
> names, just like the compatible strings.

Ok, I've renamed the "bcm" directory to "brcm" as you've described above.

> BTW, this will again create an ordering dependency with respect to my
> Generic BMIPS patch series.  If Ralf can take Andrew's updated patches
> ASAP (since they're straightforward renamings) it will make it easier
> to add/rename platforms without having to fix up merge conflicts.

Yes, I'd like to get these in -next ASAP as I have work based on them
as well.  V2 incoming...

      reply	other threads:[~2014-12-23 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 23:27 [PATCH 1/2] MIPS: Move device-trees into vendor sub-directories Andrew Bresticker
2014-12-22 23:27 ` [PATCH 2/2] MIPS: Add dtbs_install target Andrew Bresticker
     [not found] ` <1419290863-19788-1-git-send-email-abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-12-23 16:07   ` [PATCH 1/2] MIPS: Move device-trees into vendor sub-directories Florian Fainelli
     [not found]     ` <CAGVrzcZPODEbQBF8Z+_r-6H3A_S-4Mi=1ALBf87ZmEngWzDpyw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-23 16:20       ` Kevin Cernekee
2014-12-23 16:41         ` Andrew Bresticker [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=CAL1qeaH6d5DSU9UgnS4eGvFcAJXEw2iXX8czkCFd8ogdNDLEvQ@mail.gmail.com \
    --to=abrestic@chromium.org \
    --cc=arend@broadcom.com \
    --cc=cernekee@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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).