From: Christopher Covington <cov@codeaurora.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Pawel Moll <pawel.moll@arm.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: document "mach-virt" platform.
Date: Mon, 03 Feb 2014 08:46:07 -0500 [thread overview]
Message-ID: <52EF9D9F.5020600@codeaurora.org> (raw)
In-Reply-To: <20140203045638.GB4167@cbox>
Hi Christoffer,
On 02/02/2014 11:56 PM, Christoffer Dall wrote:
> On Thu, Jan 30, 2014 at 11:54:46AM -0500, Christopher Covington wrote:
>> I think it would be informative to provide pointers here to commonly used
>> paravirtualized devices, especially VirtIO PCI/MMIO.
>
> I disagree: that would only encourage limited testing or assumptions
> about these specific devices when really this platform is just a
> bare-bones platform driven by device tree which should make no
> preference, whatsoever, about which devices are used with the platform.
I'd be all for clearly stating that no assumptions can be made. Perhaps you
can explain though how providing less documentation will result in more
testing? The assertion does not currently make sense to me.
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-02-03 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 16:11 [PATCH] arm: document "mach-virt" platform Ian Campbell
2014-01-30 17:13 ` Marc Zyngier
[not found] ` <52EA8853.8080709-5wv7dgnIgG8@public.gmane.org>
2014-01-30 17:21 ` Ian Campbell
[not found] ` <1391102475.9495.44.camel-ommiHX4a84BXesXXhkcM7miJhflN2719@public.gmane.org>
2014-01-30 17:24 ` Marc Zyngier
2014-01-30 17:29 ` Ian Campbell
[not found] ` <1391098262-15944-1-git-send-email-ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2014-01-30 16:54 ` Christopher Covington
[not found] ` <52EA83D6.9050506-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-01-30 17:12 ` Stefano Stabellini
2014-02-03 4:56 ` Christoffer Dall
2014-02-03 11:14 ` Ian Campbell
2014-02-03 13:46 ` Christopher Covington [this message]
[not found] ` <52EF9D9F.5020600-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-02-03 17:41 ` Christoffer Dall
2014-01-30 17:15 ` Ian Campbell
[not found] ` <1391102149.9495.39.camel-ommiHX4a84BXesXXhkcM7miJhflN2719@public.gmane.org>
2014-01-30 17:43 ` Christopher Covington
2014-01-30 17:28 ` Arnd Bergmann
[not found] ` <201401301828.59294.arnd-r2nGTMty4D4@public.gmane.org>
2014-01-30 17:33 ` Marc Zyngier
[not found] ` <52EA8CFE.7020404-5wv7dgnIgG8@public.gmane.org>
2014-01-31 17:48 ` Rob Herring
2014-01-30 17:33 ` Ian Campbell
2014-02-03 4:54 ` Christoffer Dall
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=52EF9D9F.5020600@codeaurora.org \
--to=cov@codeaurora.org \
--cc=arnd@arndb.de \
--cc=christoffer.dall@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=will.deacon@arm.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).