All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Xu <xuwei5@hisilicon.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is the hisilicon tree maintained ?
Date: Fri, 2 Feb 2018 14:45:45 +0000	[thread overview]
Message-ID: <5A747999.3020804@hisilicon.com> (raw)
In-Reply-To: <26b7f172-c8d3-0a2e-3573-a488e3ca8ef7@linaro.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

> 
> 
> 

      reply	other threads:[~2018-02-02 14:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02  6:59 Is the hisilicon tree maintained ? Daniel Lezcano
2018-02-02 11:42 ` Wei Xu
2018-02-02 12:05   ` Daniel Lezcano
2018-02-02 12:10     ` Wei Xu
2018-02-02 13:34       ` Daniel Lezcano
2018-02-02 13:48         ` Wei Xu
2018-02-02 13:53           ` Daniel Lezcano
2018-02-02 14:04             ` Wei Xu
2018-02-02 14:29               ` Daniel Lezcano
2018-02-02 14:45                 ` Wei Xu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A747999.3020804@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.