From: Julien Grall <julien.grall@arm.com>
To: Denis Obrezkov <denisobrezkov@gmail.com>,
Hunyue Yau <hy-gsoc@hy-research.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Iain Hunter <drhunter95@gmail.com>
Subject: Re: [Xen-devel] [GSoC-2019] About the crossbar and xen
Date: Fri, 12 Jul 2019 16:00:50 +0100 [thread overview]
Message-ID: <74730e97-ed3e-1e93-603a-2e0f9730879e@arm.com> (raw)
In-Reply-To: <1de0763d-0945-378d-6838-aeae13191059@gmail.com>
On 7/11/19 7:29 PM, Denis Obrezkov wrote:
> Hi,
Hi,
> On 7/11/19 7:32 PM, Julien Grall wrote:
>
>>>
>>> What do you think?
>>
>> Have you looked at the series I pointed out earlier on? It extends Xen
>> to support other interrupt controller parent.
>>
> Yes, but you said once that these patch series wasn't accepted because
> maintainers didn't like something. So, I wanted to understand whether
> this approach is acceptable.
The series was reviewed publicly. Looking through the series, I don't
think major concern on the approach suggested.
How about you have a try at the series and see how far you can go? We
can discuss about improvement once you have the crossbar up and running.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-07-12 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 18:54 [Xen-devel] [GSoC-2019] About the crossbar and xen Denis Obrezkov
2019-07-10 19:49 ` Stefano Stabellini
2019-07-10 19:54 ` Denis Obrezkov
2019-07-10 20:17 ` Stefano Stabellini
2019-07-10 20:43 ` Denis Obrezkov
2019-07-10 23:20 ` Hunyue Yau
2019-07-11 12:50 ` Denis Obrezkov
2019-07-11 17:32 ` Julien Grall
2019-07-11 18:29 ` Hunyue Yau
2019-07-12 15:13 ` Julien Grall
2019-07-12 18:32 ` Hunyue Yau z
2019-07-15 11:36 ` Julien Grall
2019-07-11 18:29 ` Denis Obrezkov
2019-07-12 15:00 ` Julien Grall [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=74730e97-ed3e-1e93-603a-2e0f9730879e@arm.com \
--to=julien.grall@arm.com \
--cc=denisobrezkov@gmail.com \
--cc=drhunter95@gmail.com \
--cc=hy-gsoc@hy-research.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.