From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752136AbeBBOqC (ORCPT ); Fri, 2 Feb 2018 09:46:02 -0500 Received: from szxga07-in.huawei.com ([45.249.212.35]:50731 "EHLO huawei.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751643AbeBBOpz (ORCPT ); Fri, 2 Feb 2018 09:45:55 -0500 Subject: Re: Is the hisilicon tree maintained ? To: Daniel Lezcano References: <68abfa22-86fa-67db-b583-661c9f5672ce@linaro.org> <5A744EBA.7030104@hisilicon.com> <5A745526.6040006@hisilicon.com> <9f22e61e-a5d4-47b9-b8dd-71443b9aa408@linaro.org> <5A746C4A.9050604@hisilicon.com> <5A746FD6.5050603@hisilicon.com> <26b7f172-c8d3-0a2e-3573-a488e3ca8ef7@linaro.org> CC: Linux Kernel Mailing List From: Wei Xu Message-ID: <5A747999.3020804@hisilicon.com> Date: Fri, 2 Feb 2018 14:45:45 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <26b7f172-c8d3-0a2e-3573-a488e3ca8ef7@linaro.org> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.226.123] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, On 2018/2/2 14:29, Daniel Lezcano wrote: > On 02/02/2018 15:04, Wei Xu wrote: >> Hi Daniel, >> >> On 2018/2/2 13:53, Daniel Lezcano wrote: >>> On 02/02/2018 14:48, Wei Xu wrote: >>>> Hi Daniel, >>>> >>>> On 2018/2/2 13:34, Daniel Lezcano wrote: >>>>> On 02/02/2018 13:10, Wei Xu wrote: >>>>>> Hi Daniel, >>>>>> >>>>>> On 2018/2/2 12:05, Daniel Lezcano wrote: >>>>>>> On 02/02/2018 12:42, Wei Xu wrote: >>>>>>>> Hi Daniel, >>>>>>>> >>>>>>>> On 2018/2/2 6:59, Daniel Lezcano wrote: >>>>>>>>> >>>>>>>>> Hi Wei Xu, >>>>>>>>> >>>>>>>>> I found in the MAINTAINERS file the hisilicon tree is at: >>>>>>>>> >>>>>>>>> https://github.com/hisilicon/linux-hisi >>>>>>>>> >>>>>>>>> But, (except I missed it) I didn't find any update since Nov, 2017. >>>>>>>>> >>>>>>>>> Is that tree maintained ? >>>>>>>> >>>>>>>> Yes. It is still maintained. >>>>>>>> You can find update from other branches or the tags like next/dt64. >>>>>>>> I will update the master when every rc1 is released. >>>>>>> >>>>>>> Is there a development branch for something else than the DT ? >>>>>> >>>>>> Sorry, no developing branch is there. >>>>>> But we will create one if needed like the topic-acpi-mbigen branch. >>>>>> And most of development branches are kept in another git repo. >>>>> >>>>> What is the purpose of this tree? Why not rely on arm-soc? >>>> >>>> Currently it is mainly a place to pick up the patches >>>> and save the pull request. >>> >>> What is the other repo with development branches you mentioned above ? >> >> Sorry, they are private repos in the github hisilicon and are for the SoC >> enablement like hip06, hip07 and so on. >> But if you can share what kind of information you want, I can create a >> public branch in the hisilicon/linux-hisi repo if I have those. > > Actually I was expecting to see an up-to-date branch I can rely on to > base my patches. As a arm sub SoC maintainer, the patches come to me mainly are related with dts, defconfig, arch/arm/hisilicon and drivers/platform. Generally you can based your patches on rc1 and there is very few case your patches will be conflicted with others. > > Apparently there is very few dev on this tree. Why not change the tree > to arm-soc in the MAINTAINERS file ? Yes, no much development on this tree. But it is still benefit for hisilicon and the community. And other silicon vendors also do like this. Best Regards, Wei > > >