From: David Miller <davem@davemloft.net>
To: richardcochran@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Extend Time Stamping
Date: Sun, 18 Jul 2010 19:24:20 -0700 (PDT) [thread overview]
Message-ID: <20100718.192420.146333161.davem@davemloft.net> (raw)
In-Reply-To: <cover.1279391885.git.richard.cochran@omicron.at>
From: Richard Cochran <richardcochran@gmail.com>
Date: Sat, 17 Jul 2010 20:48:02 +0200
> This patch set extends the packet time stamping capabilites of the
> network stack in two ways.
>
> 1. The first patch presents a work-around for the TX software time
> stamping fallback problem cited in cd4d8fdad1f1. The idea is to add
> one inline function into each MAC driver. This function will act
> as hooks for current (and possible future) time stamping needs,
> once they are placed correctly within each MAC driver.
>
> 2. The other patches prepare the way for PHY drivers to offer time
> stamping.
>
> I am preparing a new round of patches for PTP support, but it will
> require the changes in this patch set in order to function. Thus I
> would like to have this patch set reviewed (and hopefully merged) in
> order to go forward.
Ok this looks good enough to me to toss into net-next-2.6
All applied, thanks!
prev parent reply other threads:[~2010-07-19 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 18:48 [PATCH v3 0/4] Extend Time Stamping Richard Cochran
2010-07-17 18:48 ` [PATCH 1/4] net: add driver hook for tx time stamping Richard Cochran
2010-07-17 18:48 ` [PATCH 2/4] net: preserve ifreq parameter when calling generic phy_mii_ioctl() Richard Cochran
2010-07-17 18:49 ` [PATCH 3/4] net: added a BPF to help drivers detect PTP packets Richard Cochran
2010-07-17 18:49 ` [PATCH 4/4] net: support time stamping in phy devices Richard Cochran
2010-07-19 2:24 ` David Miller [this message]
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=20100718.192420.146333161.davem@davemloft.net \
--to=davem@davemloft.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).