From: Reg Clemens <reg@dwf.com>
To: john stultz <johnstul@us.ibm.com>
Cc: James Cloos <cloos@jhcloos.com>,
davehart_gmail_exchange_tee@davehart.net, hackers@lists.ntp.org,
linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>,
Thomas Gleixner <tglx@linutronix.de>,
reg@fw.dwf.com
Subject: Re: [ntp:hackers] ntp-dev-4.2.5p235-RC build failure: MOD_NANO not #defined
Date: Wed, 21 Oct 2009 17:03:57 -0600 [thread overview]
Message-ID: <200910212303.n9LN3vFt000507@deneb.dwf.com> (raw)
In-Reply-To: <1256085838.3346.45.camel@localhost>
Isnt it just time to get rid of these MOD_ constructs in ntp?
A quick find/grep of the code shows that there are only 7 usages left
in the ntpd main line.
There are 2 in tickadj.
There are 15 in ntptime.
It would take less time to change these to the STA_*** forms than
to see this question ever come up again.
--
Reg.Clemens
reg@dwf.com
next prev parent reply other threads:[~2009-10-21 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:38 James Cloos
2009-10-20 19:27 ` [ntp:hackers] " Dave Hart
2009-10-20 20:45 ` john stultz
2009-10-20 23:22 ` James Cloos
2009-10-21 0:43 ` john stultz
2009-10-21 23:03 ` Reg Clemens [this message]
2009-10-22 1:58 ` Harlan Stenn
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=200910212303.n9LN3vFt000507@deneb.dwf.com \
--to=reg@dwf.com \
--cc=cloos@jhcloos.com \
--cc=davehart_gmail_exchange_tee@davehart.net \
--cc=hackers@lists.ntp.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@fw.dwf.com \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®