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 1/1] ntp: no longer require openssl
Date: Wed, 8 Nov 2017 18:03:10 +0100	[thread overview]
Message-ID: <20171108180310.144957c1@windsurf> (raw)
In-Reply-To: <87fu9peysf.fsf@dell.be.48ers.dk>

Hello,

On Wed, 08 Nov 2017 13:32:32 +0100, Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:  
> 
>  > Hello,
>  > On Tue,  7 Nov 2017 16:29:06 -0500, Adam Duskett wrote:  
>  >> 4.2.8p10 no longer requires openssl to compile.
>  >> 
>  >> Signed-off-by: Adam Duskett <Adamduskett@outlook.com>  
> 
>  > Peter: I'm wondering if we should apply this to next or master. It is
>  > not a bug fix per-se, but it fixes a kind of regression introduced with
>  > the bump of ntp to 4.2.8p9, which was merged in 2017.02, and brought in
>  > OpenSSL as a mandatory dependency. A user reported on Github that it
>  > increased quite a lot the installed size (due to the additional OpenSSL
>  > dependency).  
> 
>  > So, I'm tempted to apply this to master. Peter, are you OK?  
> 
> Yes. I've just applied it. I will also cherry pick to the LTS branch.

Be careful if you cherry-pick in the LTS branch: it depends on p10
version of ntp, which was committed after 2017.02 was released. I
haven't looked if the p10 bump has already been cherry-picked in the
LTS branch.

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

  reply	other threads:[~2017-11-08 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 21:29 [Buildroot] [PATCH 1/1] ntp: no longer require openssl Adam Duskett
2017-11-08 10:43 ` Thomas Petazzoni
2017-11-08 12:32   ` Peter Korsgaard
2017-11-08 17:03     ` Thomas Petazzoni [this message]
2017-11-08 18:58       ` Peter Korsgaard
2017-11-08 12:32 ` Peter Korsgaard

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=20171108180310.144957c1@windsurf \
    --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