Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8146456ybn; Tue, 1 Oct 2019 04:02:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqxIdAV1RyHVg0NmRxuWJ95urItRSh1D7urd4GgbOqHkttcy/srW4EPJTtPfdhWE4Q8Xm1mf X-Received: by 2002:a50:ac0a:: with SMTP id v10mr24681227edc.83.1569927771635; Tue, 01 Oct 2019 04:02:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569927771; cv=none; d=google.com; s=arc-20160816; b=vgGJuHoCAkXcrcCVASqRTmaIOcbEJWzSpTgaiFHerEGJfv4qSj/6rDYtqdynKx51kq X939T8+wx3cIZpG1NlyPUZOgteNi9ZGs4/DRsUt4t/RAcPeJew+SblHdkcHPpQrAtBFi YIRplqclPoTnI7zVghXbG4Sr0B2BA1fbZQ46mhIYRaRtaFnd2/3sTNv2TBXRnGhKPihu Q+Se3TIzupD6qTaSTqRqrA31Cm4kU+IO763MtYGW2o85LHP9bsOSLqyigeT+ZBqPUoVS VHaFLeCQ+AsYG3VqO1NS+PFv4lsPaqeCp5HK8fNA4FKbwgTdrqfyfdyGMGhRyIdqIcot isnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=MBD47UcNr+Fo/iucvGFF19GC0vWm8ktCywwLXKBaUCk=; b=01zFZjnxSHM72ZrZQlCALdS/5JnLfhQLY6e0CDGLfk548+hV+wxfrPCXgSbJnso8qI 4eEBScKRtYLA4W2wvfUQPJlW4VyN3tT6BK1FxlqBuiLQj9pQ4HoV2h0KRhIZ8qJ6JJk/ 3lknoDt+A+2tf2MpEXGA8kITzfyx5IPVmgpOybZMmzCeXe71EpT5KX+LyFDgkN3oV7xN RT4FMiT4iIY3mvBqRQy5QDljbxjCMFUIbEKNb282HvKFF9CKB9M864O/3QEP4puOsQg1 bp8VDD76+37GnF30ri+TIWsRpenCEpvvA+hOJ9E1/9VUj/1xeK2JolyzaCzNVaPR4Zxb X2pA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=DKAOAjhh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t26si7893592eju.238.2019.10.01.04.02.26; Tue, 01 Oct 2019 04:02:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=DKAOAjhh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730815AbfJALB0 (ORCPT + 99 others); Tue, 1 Oct 2019 07:01:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:58670 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725865AbfJALBZ (ORCPT ); Tue, 1 Oct 2019 07:01:25 -0400 Received: from mail-wm1-f42.google.com (mail-wm1-f42.google.com [209.85.128.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 11BBA21924; Tue, 1 Oct 2019 11:01:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569927684; bh=WFo4AOUfzZaJbgEqFa0H+5dWz8gP0vH+XT9yDB8pn74=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=DKAOAjhhZQekV/U0rf1A61tna9L0itLTk3ksZxH/4x8NGaaPEMB6wFbrRuMk0nE04 pmYtJv/BtN/snI8o56m6K6S3SNSX+TmnxsyTYPmUmLs0860AYsKNWKF8bA4kBcxDS0 YByxPCIlMdIoRWs6B2VsNN9AfxWvOcIyagdW+dRY= Received: by mail-wm1-f42.google.com with SMTP id 5so2865632wmg.0; Tue, 01 Oct 2019 04:01:23 -0700 (PDT) X-Gm-Message-State: APjAAAWMdUNuB/GarppTaX4wdGIJGyNMIp07vwdO2a/xIiGJNmEwBnwg hENOsPIrybNPvpudeMcnBa9ASTgz9my4kEvjCH4= X-Received: by 2002:a1c:2b41:: with SMTP id r62mr3025307wmr.47.1569927682563; Tue, 01 Oct 2019 04:01:22 -0700 (PDT) MIME-Version: 1.0 References: <20190919052822.10403-1-jagan@amarulasolutions.com> <20190919052822.10403-5-jagan@amarulasolutions.com> <4177305.6QI6aNXrAv@phil> In-Reply-To: From: Chen-Yu Tsai Date: Tue, 1 Oct 2019 19:01:09 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 4/6] arm64: dts: rockchip: Rename roc-pc with libretech notation To: Jagan Teki Cc: Heiko Stuebner , Mark Rutland , devicetree , Da Xue , linux-kernel , "open list:ARM/Rockchip SoC..." , Rob Herring , Akash Gajjar , Levin Du , linux-amarula , linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 1, 2019 at 6:34 PM Jagan Teki wrote: > > On Mon, Sep 30, 2019 at 3:02 AM Heiko Stuebner wrote: > > > > Hi Jagan, > > > > Am Donnerstag, 19. September 2019, 07:28:20 CEST schrieb Jagan Teki: > > > Though the ROC-PC is manufactured by firefly, it is co-designed > > > by libretch like other Libretech computer boards from allwinner, > > > amlogic does. > > > > > > So, it is always meaningful to keep maintain those vendors who > > > are part of design participation so-that the linux mainline > > > code will expose outside world who are the makers of such > > > hardware prototypes. > > > > > > So, rename the existing rk3399-roc-pc.dts with libretch notation, > > > rk3399-libretech-roc-rk3399-pc.dts > > > > > > Signed-off-by: Jagan Teki > > > --- > > > arch/arm64/boot/dts/rockchip/Makefile | 2 +- > > > .../{rk3399-roc-pc.dts => rk3399-libretech-roc-rk3399-pc.dts} | 0 > > > > Somewhat "randomly" renaming files for "exposure" of the maker isn't the > > way to go. Especially as the file name itself is merely a handle and not > > meant for fame. The board filename should mainly enable developers to > > hopefully the correct board file to use/change - and "rk3399-roc-pc" > > is sufficiently unique to do that. > > > > Similar to how the NanoPi boards do that. > > > > And renames not only loose the history of changes but also in this case > > the file is in the kernel since july 2018 - more than a year, so this might > > actually affect the workflow of someone. > > Yes, I agreed this point. > > > > > So I'd really expect an actual technical reason for a rename. > > This changes purely based on the recent changes on naming conventions > that have been followed in amlogic and allwinner with regards to > libretech [1]. I have seen few Bananapi boards from Allwinner H3 has > been converted as per Libretech computer recently. I assume these The DTS file for AML-S905X-CC has never been renamed. The ALL-H3-CC was only reworked to split out the common bits to accommodate the different SoC (H3 vs H5) variants for the same board. Even after the rework, the board DTS files retained their original naming scheme. Same goes for the Bananapi M2+. However we have never renamed Bananapi files to Libretech. Since Libre Computer and Firefly both have the ROC-RK3399-PC, renaming it is likely to cause some confusion. ChenYu > changes are because libretech has part of co-designed vendor and also > open source forum supported for these hardware. > > For further information, may be Da Xue can comment on this. > > [1] https://libre.computer/products/boards/ > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel