From: Bastian Stender <bst@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] ntp: update/transform configure options
Date: Mon, 26 Mar 2018 11:12:56 +0200 [thread overview]
Message-ID: <b3dba423-4d5e-21f7-c36b-72a94f9c46aa@pengutronix.de> (raw)
In-Reply-To: <20180326061738.qdqxr34a5jcu5j32@pengutronix.de>
On 03/26/2018 08:17 AM, Michael Olbrich wrote:
> On Wed, Mar 21, 2018 at 04:59:47PM +0100, Bastian Stender wrote:
>> Use proper ptx/endis and ptx/wwo options, checked and corrected
>> configure options using configure_helper.py.
>>
>> Some configure options changed over time:
>>
>> --enable-ARCRON_MSF is actually --enable-ARCRON-MSF
>>
>> --enable-arlib is now --with-arlib
>>
>> --enable-udp-wildcard removed in 4848b7bf9 ("Lose UDP_WILDCARD_DELIVERY")
>>
>> --enable-MSFEES removed in ba7975983 ("[Bug 340, 342] Deprecate broken TRAK and MSF EES refclocks")
>> --enable-TRAK removed in ba7975983 ("[Bug 340, 342] Deprecate broken TRAK and MSF EES refclocks")
>>
>> --enable-PTBACTS removed in e0da3f545 ("Remove PTB and USNO lint")
>>
>> Signed-off-by: Bastian Stender <bst@pengutronix.de>
>> ---
>> Changes since (implicit) v1:
>> - use ptx/endis, ptx/wwo and ptx/ifdef where appropriate
>> - revisit configure options with helper script
>> - sorted options according to configure
>
> Thanks. I've pushed it with a followup commit with some more
> cleanup. Mostly removing options that where bogus or should not be
> configurable. It would be great if you could test this to make sure I
> didn't break anything.
I've tested it and it works as expected. Thanks.
> Do you have any opinion on the remaining options? I think there are
> still too many, but I don't know enough to make a good decision.
Me neither, so I think we should stick with the current state.
Bastian
--
Pengutronix e.K.
Industrial Linux Solutions
http://www.pengutronix.de/
Peiner Str. 6-8, 31137 Hildesheim, Germany
Amtsgericht Hildesheim, HRA 2686
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-03-26 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 15:59 Bastian Stender
2018-03-26 6:17 ` Michael Olbrich
2018-03-26 9:12 ` Bastian Stender [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=b3dba423-4d5e-21f7-c36b-72a94f9c46aa@pengutronix.de \
--to=bst@pengutronix.de \
--cc=ptxdist@pengutronix.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