Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] ntp: Adding pps support to ntpd
Date: Thu, 16 Oct 2014 11:30:02 +0200	[thread overview]
Message-ID: <20141016113002.37bd449f@free-electrons.com> (raw)
In-Reply-To: <1413405475-5179-2-git-send-email-matthew.weber@rockwellcollins.com>

Dear Matt Weber,

On Wed, 15 Oct 2014 15:37:55 -0500, Matt Weber wrote:

> +config BR2_PACKAGE_NTP_NTPD_ATOM_PPS
> +	bool "ntpd-pps"

I'd use "PPS support" here instead.

> +	depends on BR2_PACKAGE_NTP_NTPD
> +	select BR2_PACKAGE_PPS_TOOLS
> +	help
> +	  Compile ntpd with the ability to use an ATOM PPS source.
> +
>  config BR2_PACKAGE_NTP_NTPDATE
>  	bool "ntpdate"
>  	help
> diff --git a/package/ntp/ntp.mk b/package/ntp/ntp.mk
> index 7c2cb8e..51598ba 100644
> --- a/package/ntp/ntp.mk
> +++ b/package/ntp/ntp.mk
> @@ -34,6 +34,11 @@ else
>  	NTP_CONF_OPTS += --without-ntpsnmpd
>  endif
>  
> +ifeq ($(BR2_PACKAGE_NTP_NTPD_ATOM_PPS),y)
> +	NTP_CONF_OPTS += --enable-ATOM
> +	NTP_DEPENDENCIES += pps-tools
> +endif

Can you add the corresponding:

else
	NTP_CONF_OPTS += --disable-ATOM
endif

We like to be explicit about configuration options when possible.

With that fixed, you can resend this patch with my:

Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

(I did built test this).

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-16  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 20:37 [Buildroot] [PATCH 1/2] pps-tools: new package Matt Weber
2014-10-15 20:37 ` [Buildroot] [PATCH 2/2] ntp: Adding pps support to ntpd Matt Weber
2014-10-16  9:30   ` Thomas Petazzoni [this message]
2014-10-16  9:24 ` [Buildroot] [PATCH 1/2] pps-tools: new package Thomas Petazzoni
2014-10-16 13:44 ` Ryan Barnett

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=20141016113002.37bd449f@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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