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] haveged: for sparc we need generic clockgettime
Date: Sun, 9 Aug 2015 11:19:24 +0200	[thread overview]
Message-ID: <20150809111924.2f1314e0@free-electrons.com> (raw)
In-Reply-To: <20150809084740.GA19849@waldemar-brodkorb.de>

Dear Waldemar Brodkorb,

On Sun, 9 Aug 2015 10:47:40 +0200, Waldemar Brodkorb wrote:
> This fixes autobuilder error:
> http://autobuild.buildroot.net/results/5b8bbc30f347140309ab2f81e1fe50f517356a3e/
> 
> As sparcv9 assembly is used, we need to enable generic clock_gettime
> for sparcv8 systems.
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
>  package/haveged/haveged.mk |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/package/haveged/haveged.mk b/package/haveged/haveged.mk
> index c68f766..489564a 100644
> --- a/package/haveged/haveged.mk
> +++ b/package/haveged/haveged.mk
> @@ -9,6 +9,10 @@ HAVEGED_SITE = http://www.issihosts.com/haveged
>  HAVEGED_LICENSE = GPLv3+
>  HAVEGED_LICENSE_FILES = COPYING
>  
> +ifeq ($(BR2_sparc),y)

So this should be:

ifeq ($(BR2_sparc_v8)$(BR2_sparc_leon3),y)

Right? We indeed don't support any SPARCv9 at the moment, but it's
probably better to be more specific. What do you think?

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

  reply	other threads:[~2015-08-09  9:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09  8:47 [Buildroot] [PATCH] haveged: for sparc we need generic clockgettime Waldemar Brodkorb
2015-08-09  9:19 ` Thomas Petazzoni [this message]
2015-08-09  9:29   ` Waldemar Brodkorb
2015-08-09  9:40     ` Thomas Petazzoni

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=20150809111924.2f1314e0@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