From: Daniel Walker <dwalker@fifo99.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Patrick Ohly <patrick.ohly@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH NET-NEXT 01/10] clocksource: allow usage independent of timekeeping.c
Date: Wed, 04 Feb 2009 13:04:59 -0800 [thread overview]
Message-ID: <1233781499.15119.135.camel@desktop> (raw)
In-Reply-To: <1233777982.6994.51.camel@localhost.localdomain>
On Wed, 2009-02-04 at 12:06 -0800, john stultz wrote:
> The duplication is only at a very low level. He could not reuse the
> established clocksource system without really breaking its semantics.
He gave a link to the first version,
http://kerneltrap.org/mailarchive/linux-netdev/2008/11/19/4164204
What specific semantics is he breaking there?
Daniel
next prev parent reply other threads:[~2009-02-04 21:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 13:01 clock synchronization utility code Patrick Ohly
2009-02-04 13:01 ` [PATCH NET-NEXT 01/10] clocksource: allow usage independent of timekeeping.c Patrick Ohly
2009-02-04 13:01 ` [PATCH NET-NEXT 02/10] time sync: generic infrastructure to map between time stamps generated by a time counter and system time Patrick Ohly
2009-02-04 19:44 ` john stultz
2009-02-05 10:21 ` Patrick Ohly
2009-02-09 17:02 ` Patrick Ohly
2009-02-09 19:27 ` John Stultz
2009-02-09 21:46 ` Patrick Ohly
2009-02-09 21:54 ` John Stultz
2009-02-09 22:57 ` David Miller
2009-02-04 14:03 ` [PATCH NET-NEXT 01/10] clocksource: allow usage independent of timekeeping.c Daniel Walker
2009-02-04 14:46 ` Patrick Ohly
2009-02-04 15:09 ` Daniel Walker
2009-02-04 15:24 ` Patrick Ohly
2009-02-04 19:25 ` john stultz
2009-02-04 19:40 ` Daniel Walker
2009-02-04 20:06 ` john stultz
2009-02-04 21:04 ` Daniel Walker [this message]
2009-02-04 21:15 ` john stultz
2009-02-05 0:18 ` Daniel Walker
2009-02-05 10:21 ` Patrick Ohly
-- strict thread matches above, loose matches on Subject: below --
2009-02-12 14:57 [PATCH NET-NEXT 0/10] hardware time stamping with new fields in shinfo Patrick Ohly
2009-02-12 15:00 ` [PATCH NET-NEXT 01/10] clocksource: allow usage independent of timekeeping.c Patrick Ohly
2009-02-12 15:03 [PATCH NET-NEXT 0/10] hardware time stamping with new fields in shinfo Patrick Ohly
2009-02-12 15:03 ` [PATCH NET-NEXT 01/10] clocksource: allow usage independent of timekeeping.c Patrick Ohly
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=1233781499.15119.135.camel@desktop \
--to=dwalker@fifo99.com \
--cc=davem@davemloft.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patrick.ohly@intel.com \
--cc=tglx@linutronix.de \
/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