All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/numactl: Fix uClibc compile breakage after musl compile fix
Date: Wed, 24 Feb 2016 11:57:37 +0100	[thread overview]
Message-ID: <20160224115737.7af50732@free-electrons.com> (raw)
In-Reply-To: <1455393768-26580-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sat, 13 Feb 2016 21:02:48 +0100, Bernd Kuhls wrote:
> Fixes
> http://autobuild.buildroot.net/results/316/3160fb32fbb6990b0bb268524dcea02a1f6880a7/
> http://autobuild.buildroot.net/results/961/9616f09e7cbd020134ba72853acaa28a308432a3//
> and others
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v3: use a better fix (Thomas)
> v2: updated patch to consider improvements suggested by upstream

Instead of this patch, I've committed a patch that simply replaces our
private patch with a NUMACTL_PATCH variable that references the two
upstream commits that fix the numactl build issue for both musl and
uclibc.

Thanks a lot for having worked with upstream on this, definitely
appreciated!

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

      parent reply	other threads:[~2016-02-24 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-13 20:02 [Buildroot] [PATCH v3 1/1] package/numactl: Fix uClibc compile breakage after musl compile fix Bernd Kuhls
2016-02-14 12:51 ` Thomas Petazzoni
2016-02-14 14:11   ` Bernd Kuhls
2016-02-15 22:30     ` Thomas Petazzoni
2016-02-24 10:57 ` 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=20160224115737.7af50732@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.