lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL1qeaH6d5DSU9UgnS4eGvFcAJXEw2iXX8czkCFd8ogdNDLEvQ@mail.gmail.com>
Date:	Tue, 23 Dec 2014 08:41:23 -0800
From:	Andrew Bresticker <abrestic@...omium.org>
To:	Kevin Cernekee <cernekee@...il.com>
Cc:	Florian Fainelli <f.fainelli@...il.com>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Linux-MIPS <linux-mips@...ux-mips.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Arend van Spriel <arend@...adcom.com>
Subject: Re: [PATCH 1/2] MIPS: Move device-trees into vendor sub-directories

On Tue, Dec 23, 2014 at 8:20 AM, Kevin Cernekee <cernekee@...il.com> wrote:
> On Tue, Dec 23, 2014 at 8:07 AM, Florian Fainelli <f.fainelli@...il.com> wrote:
>> 2014-12-22 15:27 GMT-08:00 Andrew Bresticker <abrestic@...omium.org>:
>>> Move the MIPS device-trees into the appropriate vendor sub-directories.
>>>
>>> Signed-off-by: Andrew Bresticker <abrestic@...omium.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...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ