xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Zoltan Kiss <zoltan.kiss@linaro.org>,
	Julien Grall <julien.grall@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	stefano.stabellini@citrix.com,
	Zoltan Kiss <zoltan.kiss@huawei.com>
Subject: Re: [PATCH] xen/arm: gic-hip04: Resync the driver with the GICv2
Date: Mon, 1 Jun 2015 12:13:17 +0100	[thread overview]
Message-ID: <556C3E4D.1080304@citrix.com> (raw)
In-Reply-To: <5559EAD3.7030000@linaro.org>

Hi,

On 18/05/15 14:36, Zoltan Kiss wrote:
> 
> 
> On 15/05/15 22:08, Julien Grall wrote:
>> Hi Zoltan,
>>
>> On 07/05/2015 13:37, Zoltan Kiss wrote:
>>
>>> On 07/05/15 10:32, Ian Campbell wrote:
>>>> On Thu, 2015-05-07 at 09:52 +0100, Zoltan Kiss wrote:
>>>>> Looks good at first glance, let me try it on a board.
>>>>>
>>>>> On 06/05/15 19:52, Julien Grall wrote:
>>>> [...]
>>>>>> I'm concerned to see a newly driver (pushed last march) already
>>>>>> orphan.
>>>>>> Does Huawei still plan to maintain this driver?
>>>>
>>>> I share Julien's concerns here.
>>>>
>>>> It would be good if those listed in the MAINTAINERS file for this
>>>> device
>>>> would respond reasonably promptly to mails such as [1] and try to keep
>>>> on top of things or to find a {replacement /co-}maintainer who can do
>>>> so.
>>>
>>> As I said, I've missed that thread entirely (not that hard given the
>>> traffic of the list), but now I've improved my mail filters to make sure
>>> I don't miss a mail where my Huawei address is on the Cc.
>>> We are also looking to add new co-maintainers, because nowadays I'm
>>> working on other projects.
>>> I need a few days to test the patch as my Xen test environment is not
>>> available right now.
>>
>> Ping? Were you able to test it?
> 
> One of my colleague is doing that, to spread experience. It's going
> slower for him obviously to set up an enviroment, but we are working on
> that.

Ping? Was your colleague able to setup Xen? Aside gic-hip04 is not
booting on Xen, this is also a blocker from few patch series based on
this rebase (GICv2 on GICv3, 128 VCPUs support...).

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-06-01 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 18:52 [PATCH] xen/arm: gic-hip04: Resync the driver with the GICv2 Julien Grall
2015-05-07  8:52 ` Zoltan Kiss
2015-05-07  9:32   ` Ian Campbell
2015-05-07 12:37     ` Zoltan Kiss
2015-05-15 21:08       ` Julien Grall
2015-05-18 13:36         ` Zoltan Kiss
2015-06-01 11:13           ` Julien Grall [this message]
2015-06-01 11:18             ` Ian Campbell
2015-06-01 11:25             ` Zoltan Kiss
2015-06-01 12:11               ` Julien Grall
2015-06-01 13:18                 ` Zoltan Kiss
2015-06-01 15:34                   ` Julien Grall
2015-06-09 13:03                     ` Shameerali Kolothum Thodi
2015-06-10 18:23                       ` Julien Grall
2015-06-03 10:35               ` Ian Campbell

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=556C3E4D.1080304@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zoltan.kiss@huawei.com \
    --cc=zoltan.kiss@linaro.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;
as well as URLs for NNTP newsgroup(s).