linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yong, Jonathan" <jonathan.yong@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support
Date: Wed, 17 Aug 2016 16:51:43 +0800	[thread overview]
Message-ID: <57B4259F.2040302@intel.com> (raw)
In-Reply-To: <20160816133715.GA30825@localhost>

On 08/16/2016 21:37, Bjorn Helgaas wrote:
>> Looks like there is still this compile warning to fix:
>> http://patchwork.ozlabs.org/patch/634825/
> 
> That report was from June 16, and I think I fixed the warning already.
> Or do you still see the warning?  I don't see it myself.
> 
> Bjorn
> 

If that is fixed, I don't anything else to add.

  reply	other threads:[~2016-08-17  8:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 19:05 [PATCH v6 0/3] PCI: Precision Time Measurement support Bjorn Helgaas
2016-06-13 19:05 ` [PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support Bjorn Helgaas
2016-08-10  2:58   ` Yong, Jonathan
2016-08-15 18:59     ` Bjorn Helgaas
2016-08-16  8:04       ` Yong, Jonathan
2016-08-16 13:37         ` Bjorn Helgaas
2016-08-17  8:51           ` Yong, Jonathan [this message]
2016-08-22 17:01           ` Bjorn Helgaas
2016-08-23  0:13             ` Yong, Jonathan
2016-06-13 19:05 ` [PATCH v6 2/3] PCI: Add pci_enable_ptm() for drivers to enable PTM on endpoints Bjorn Helgaas
2016-06-13 19:05 ` [PATCH v6 3/3] PCI: Add PTM clock granularity information Bjorn Helgaas
2016-06-13 19:42   ` kbuild test robot
2016-07-19 21:19 ` [PATCH v6 0/3] PCI: Precision Time Measurement support Bjorn Helgaas
2016-07-19 23:49   ` Yong, Jonathan
2016-08-15 18:51     ` Bjorn Helgaas
2016-08-16  1:27       ` Yong, Jonathan
2016-08-23 21:42 ` Bjorn Helgaas
2016-08-24  1:09   ` 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=57B4259F.2040302@intel.com \
    --to=jonathan.yong@intel.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).