linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Yong, Jonathan" <jonathan.yong@intel.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [RFC v4] PCI: PTM Driver
Date: Fri, 29 Apr 2016 09:17:50 -0500	[thread overview]
Message-ID: <20160429141750.GB949@localhost> (raw)
In-Reply-To: <1461047358-4736-1-git-send-email-jonathan.yong@intel.com>

On Tue, Apr 19, 2016 at 06:29:17AM +0000, Yong, Jonathan wrote:
> Hello LKML,
> 
> This is a preliminary implementation of the PTM[1] support driver. This driver
> has only been tested against a virtual PCI bus since there are no known
> endpoints utilizing it yet.

What sort of testing is this, exactly?  Is this using a software model
of devices that support PTM?

When will hardware that supports PTM be available to you for testing?
When will it be available on the market?

I'm trying to figure out whether there's any benefit to merging
something before it is useful to anybody.

Bjorn

  parent reply	other threads:[~2016-04-29 14:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  6:29 [RFC v4] PCI: PTM Driver Yong, Jonathan
2016-04-19  6:29 ` [PATCH] PCI: PTM preliminary implementation Yong, Jonathan
2016-04-29 16:20   ` Bjorn Helgaas
2016-04-30 12:19     ` Bjorn Helgaas
2016-05-10  3:52     ` Yong, Jonathan
2016-05-08  2:38   ` Bjorn Helgaas
2016-05-09  3:11     ` Yong, Jonathan
2016-05-09 13:35       ` Bjorn Helgaas
2016-04-27 23:18 ` [RFC v4] PCI: PTM Driver Yong, Jonathan
2016-04-29 14:17 ` Bjorn Helgaas [this message]
2016-05-03  9:02   ` Yong, Jonathan
2016-05-03 14:55     ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2016-04-19  6:24 Yong, Jonathan

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=20160429141750.GB949@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=jonathan.yong@intel.com \
    --cc=linux-pci@vger.kernel.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).