From: Flavio Leitner <fbl@redhat.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: linuxptp-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Ben Hutchings <bhutchings@solarflare.com>
Subject: Re: [Linuxptp-devel] RFC [PATCH 2/3] PTP: use flags to request HW features
Date: Thu, 31 Oct 2013 23:34:19 -0200 [thread overview]
Message-ID: <20131101013419.GH4202@plex.lan> (raw)
In-Reply-To: <20131031071256.GB5226@netboy>
On Thu, Oct 31, 2013 at 08:12:58AM +0100, Richard Cochran wrote:
> On Wed, Oct 30, 2013 at 07:48:41PM -0200, Flavio Leitner wrote:
> > On Wed, Oct 30, 2013 at 05:00:36PM -0200, Flavio Leitner wrote:
> > > Currently the user space can't tell which delay mechanism
> > > (E2E/P2P) or transport is needed in the ioctl(). Therefore,
> > > PTP silently fails when the hardware doesn't support a
> > > certain delay mechanism or transport.
>
> [ For netdev readers, the text below repeats what I posted to the
> linuxptp-devel list. ]
I am reconsidering about extending ethtool instead, so I'd like to
drop these patches for now.
Thanks Richard and Jacob for the contributions,
fbl
next prev parent reply other threads:[~2013-11-01 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1383159637-8165-1-git-send-email-fbl@redhat.com>
[not found] ` <1383159637-8165-3-git-send-email-fbl@redhat.com>
2013-10-30 21:48 ` RFC [PATCH 2/3] PTP: use flags to request HW features Flavio Leitner
2013-10-31 7:12 ` [Linuxptp-devel] " Richard Cochran
2013-11-01 1:34 ` Flavio Leitner [this message]
[not found] ` <1383159637-8165-4-git-send-email-fbl@redhat.com>
2013-10-30 21:50 ` [PATCH 3/3] e1000e: PTP: provide hardware features Flavio Leitner
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=20131101013419.GH4202@plex.lan \
--to=fbl@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=linuxptp-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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).