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 11:42:50 +0000 [thread overview]
Message-ID: <5A744EBA.7030104@hisilicon.com> (raw)
In-Reply-To: <68abfa22-86fa-67db-b583-661c9f5672ce@linaro.org>
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.
Best Regards,
Wei
>
> Thanks?
>
> -- Daniel
>
>
next prev parent reply other threads:[~2018-02-02 11:43 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 [this message]
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
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=5A744EBA.7030104@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox