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]
Date:   Fri, 2 Feb 2018 15:29:44 +0100
From:   Daniel Lezcano <daniel.lezcano@...aro.org>
To:     Wei Xu <xuwei5@...ilicon.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Is the hisilicon tree maintained ?

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.

Apparently there is very few dev on this tree. Why not change the tree
to arm-soc in the MAINTAINERS file ?



-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ