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] [pull request] Pull request for branch perf-elfutils
Date: Mon, 7 Jan 2013 23:39:24 +0100	[thread overview]
Message-ID: <20130107233924.35c4d87f@skate> (raw)
In-Reply-To: <87ip78bp47.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Mon, 07 Jan 2013 23:32:56 +0100, Peter Korsgaard wrote:

> Thanks everyone, committed series.

Thanks for merging them. Hopefully, it won't make the autobuilders
explode too much.

> Thomas, please don't forget to (try to) send these patches upstream so
> we don't have to maintain them ourselves in the future.

Which ones exactly? The big fat patches we are downloading from
fedorahosted.org? Our patches?

All our patches are really specific to uClibc support, and seeing the
number of glibc-isms in elfutils, I am not sure the maintainers will be
interested in making it uClibc friendly. But it's maybe worth trying.

One nice thing that could be done is migrate the linux-kernel-module.c
thing to use nftw(), so we could drop the fts() mess.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-01-07 22:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 15:22 [Buildroot] [pull request] Pull request for branch perf-elfutils Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 01/15] package: support multiple patches Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 02/15] docs/manual: update to mention the multiple patches support Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 03/15] elfutils: new package Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 04/15] elfutils: make it possible to only install the libraries Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 05/15] perf: new package Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 06/15] perf: allow build against libelf when available Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 07/15] perf: add kernel version checks Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 08/15] argp-standlone: build position independent code Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 09/15] elfutils: towards uClibc support: argp-standalone usage Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 10/15] elfutils: towards uClibc support: solve memcpy problem Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 11/15] elfutils: towards uClibc support: requires largefile Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 12/15] elfutils: towards uClibc support: gettext Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 13/15] elfutils: towards uClibc support: FTS functions Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 14/15] elfutils: towards uClibc support: disable po build Thomas Petazzoni
2013-01-06 15:22 ` [Buildroot] [PATCH 15/15] elfutils: make available on uClibc toolchains Thomas Petazzoni
2013-01-07 22:32 ` [Buildroot] [pull request] Pull request for branch perf-elfutils Peter Korsgaard
2013-01-07 22:39   ` Thomas Petazzoni [this message]
2013-01-08  7:18     ` 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=20130107233924.35c4d87f@skate \
    --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