From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: <linux-arm-kernel@lists.infradead.org>, <kvmarm@lists.cs.columbia.edu>
Cc: Marc Zyngier <maz@kernel.org>,
"Tangnianyao \(ICT\)" <tangnianyao@huawei.com>
Subject: [Question-GIC-v4.1] Plan on GIC-v4.1 driver development
Date: Tue, 17 Sep 2019 10:15:41 +0800 [thread overview]
Message-ID: <40d7276c-54a3-0cca-a207-217459850c21@hisilicon.com> (raw)
Hi Marc,
This is from Nianyao Tang.
I'm planning to do some verification on our GIC-v4.1 implement. I would like some
information about linux GIC-v4.1 driver. When will linux support GIC-v4.1 or what's
the plan on developing GIC-v4.1 driver?
Thanks,
Nianyao.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-09-17 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 2:15 Shaokun Zhang [this message]
2019-09-17 9:23 ` [Question-GIC-v4.1] Plan on GIC-v4.1 driver development Marc Zyngier
2019-09-18 9:58 ` Marc Zyngier
2019-09-19 1:32 ` Shaokun Zhang
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=40d7276c-54a3-0cca-a207-217459850c21@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=tangnianyao@huawei.com \
/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).