From: shhuiw@foxmail.com (=?gb18030?B?V2FuZyBTaGVuZy1IdWk=?=)
To: linux-arm-kernel@lists.infradead.org
Subject: about the patch " [v2] arm64: pci: add support for pci_mmap_page_range"
Date: Wed, 13 Jul 2016 14:10:04 +0800 [thread overview]
Message-ID: <tencent_450FC44868A4D84249E2AB9D@qq.com> (raw)
Hi Jerin & Will,
Sorry to trouble you!
I found your patch https://patchwork.codeaurora.org/patch/2059/ and thought it's
helpful as many dev tools will access the resourceX file for different devices/drivers,
e.g nvme-cli for NVMe.
As for the ?legacy /proc interface?, I think it should be another topic: you have to
modify the proc for pci and handle various tools broken. But for exposing resourceX, it does work.
I wonder why this patch is not accepted into upstream? Or newer version is available?
------------------
Regards,
Wang Sheng-Hui
reply other threads:[~2016-07-13 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_450FC44868A4D84249E2AB9D@qq.com \
--to=shhuiw@foxmail.com \
--cc=linux-arm-kernel@lists.infradead.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).