linux-kernel - Re: [PATCH v2 06/15] arm: dts: Add devicetree for OrangePi 2G IoT board

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOesGMgSxwcmBLDvxsvcCJ9-NvJ3-wK8fZBZV2ZNuzAa1idi3w@mail.gmail.com>
Date:   Mon, 3 Dec 2018 09:11:05 -0800
From:   Olof Johansson <olof@...om.net>
To:     Rob Herring <robh+dt@...nel.org>
Cc:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        Arnd Bergmann <arnd@...db.de>,
        Thomas Gleixner <tglx@...utronix.de>,
        Jason Cooper <jason@...edaemon.net>,
        Marc Zyngier <marc.zyngier@....com>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.com>,
        Andreas Färber <afaerber@...e.de>,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        DTML <devicetree@...r.kernel.org>, linux-serial@...r.kernel.org,
        Amit Kucheria <amit.kucheria@...aro.org>,
        LinusW <linus.walleij@...aro.org>, zhao_steven@....net,
        overseas.sales@...soc.com
Subject: Re: [PATCH v2 06/15] arm: dts: Add devicetree for OrangePi 2G IoT board

On Mon, Dec 3, 2018 at 7:54 AM Rob Herring <robh+dt@...nel.org> wrote:
>
> On Tue, Nov 20, 2018 at 9:38 PM Manivannan Sadhasivam
> <manivannan.sadhasivam@...aro.org> wrote:
> >
> > Add initial devicetree support for OrangePi 2G IoT board from Xunlong.
> >
> > Signed-off-by: Andreas Färber <afaerber@...e.de>
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> > ---
> >  arch/arm/boot/dts/Makefile                    |  2 +
> >  .../boot/dts/rda8810pl-orangepi-2g-iot.dts    | 40 +++++++++++++++++++
> >  2 files changed, 42 insertions(+)
> >  create mode 100644 arch/arm/boot/dts/rda8810pl-orangepi-2g-iot.dts
> >
> > diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> > index b0e966d625b9..a0fdad8f10dd 100644
> > --- a/arch/arm/boot/dts/Makefile
> > +++ b/arch/arm/boot/dts/Makefile
> > @@ -806,6 +806,8 @@ dtb-$(CONFIG_ARCH_QCOM) += \
> >         qcom-msm8974-sony-xperia-castor.dtb \
> >         qcom-msm8974-sony-xperia-honami.dtb \
> >         qcom-mdm9615-wp8548-mangoh-green.dtb
> > +dtb-$(CONFIG_ARCH_RDA) += \
> > +       rda8810pl-orangepi-2g-iot.dtb
> >  dtb-$(CONFIG_ARCH_REALVIEW) += \
>
> Question for Arnd/Olof: can we *please* start putting new SoC families
> in sub-dirs?

I think we're at a point where it's becoming quite awkward to keep it
in a flat directory, yes.

Best way to handle this is usually right before the closing of a merge
window, so let's do it then. It'll be a conflict-ridden mess if we try
to stage something in -next, so I'd rather just do it directly in our
tree as a one-shot thing.


-Olof