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] package/racehound: bump and fix dependencies
Date: Wed, 13 Apr 2016 22:32:31 +0200	[thread overview]
Message-ID: <20160413223231.781d281f@free-electrons.com> (raw)
In-Reply-To: <1460579077-1219-1-git-send-email-yann.morin.1998@free.fr>

Hello,

On Wed, 13 Apr 2016 22:24:37 +0200, Yann E. MORIN wrote:
> As pointed out by Arnout, racehound does not require kernel headers
> 3.14-or-later. So, drop this depenency.
> 
> It stills require a kernel >= 3.14 to build and run, but we really hae

hae -> have

> no way to express that dependency as Kconfig options.
> 
> Besides, racehound oes not build with kernel 4.5 because the struct

oes -> does

> modules has been updated. Bump racehound to fix that build failure.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/racehound/Config.in    | 6 ++----
>  package/racehound/racehound.mk | 2 +-
>  2 files changed, 3 insertions(+), 5 deletions(-)

Applied to master after fixing the typos, thanks.

Also, I see that racehound is fetched from github and does not have a
hash file. This definitely calls for a follow-up patch :-)

Thanks!

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

      reply	other threads:[~2016-04-13 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 20:24 [Buildroot] [PATCH] package/racehound: bump and fix dependencies Yann E. MORIN
2016-04-13 20:32 ` Thomas Petazzoni [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=20160413223231.781d281f@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