mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Fabian Pflug <f.pflug@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] ntp: make sntp configureable
Date: Fri, 29 Aug 2025 11:46:21 +0200	[thread overview]
Message-ID: <20250829094621.2619637-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250814095452.1950806-1-f.pflug@pengutronix.de>

Thanks, applied as 6f4351b085dd7be2a877eac808eda23af7ebe6a4.

Michael

[sent from post-receive hook]

On Fri, 29 Aug 2025 11:46:21 +0200, Fabian Pflug <f.pflug@pengutronix.de> wrote:
> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
> Message-Id: <20250814095452.1950806-1-f.pflug@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/ntp.in b/rules/ntp.in
> index 2d85c8fac018..0d80840c2a16 100644
> --- a/rules/ntp.in
> +++ b/rules/ntp.in
> @@ -97,6 +97,17 @@ config NTP_CRYPTO
>  	help
>  	  FIXME: This item needs to be documented
>  
> +config NTP_SNTP
> +	bool
> +	prompt "build SNTP"
> +	help
> +	  Simple Network Time Protocol is a subset of the Network
> +	  Time Protocol (NTP). SNTP can be used when the ultimate
> +	  performance of a full NTP implementation based on
> +	  RFC 1305 is neither needed nor justified.
> +	  It is strongly recommended that SNTP be used only at
> +	  the extremities of the synchronization subnet.
> +
>  comment "Clock drivers"
>  
>  config NTP_ALL_CLOCK_DRIVERS
> @@ -176,4 +187,3 @@ endif
>  
>  comment "NTP conflicts with OpenNTPD"
>  	depends on NTP && OPENNTPD
> -
> diff --git a/rules/ntp.make b/rules/ntp.make
> index 9c6c9555de07..42902364578e 100644
> --- a/rules/ntp.make
> +++ b/rules/ntp.make
> @@ -128,7 +128,7 @@ NTP_CONF_OPT	:= \
>  	--disable-kmem \
>  	--enable-accurate-adjtime \
>  	--disable-simulator \
> -	--without-sntp \
> +	--$(call ptx/wwo, PTXCONF_NTP_SNTP)-sntp \
>  	--without-ntpsnmpd \
>  	--$(call ptx/endis, PTXCONF_NTP_SLEW_ALWAYS)-slew-always \
>  	--$(call ptx/endis, PTXCONF_NTP_STEP_SLEW)-step-slew \
> @@ -180,6 +180,14 @@ ifdef PTXCONF_NTP_NTPD
>  	@$(call install_alternative, ntp, 0, 0, 0644, /etc/ntp-server.conf)
>  endif
>  
> +#	#
> +#	# sntp client
> +#	#
> +ifdef PTXCONF_NTP_SNTP
> +	@$(call install_copy, ntp, 0, 0, 0755, -, \
> +		/usr/sbin/sntp)
> +endif
> +
>  ifdef PTXCONF_NTP_NTPD_STARTSCRIPT
>  	@$(call install_alternative, ntp, 0, 0, 0755, /etc/init.d/ntp-server)
>  



      reply	other threads:[~2025-08-29  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  9:54 [ptxdist] [PATCH] " Fabian Pflug
2025-08-29  9:46 ` Michael Olbrich [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=20250829094621.2619637-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=f.pflug@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