From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] More external toolchain fixes
Date: Mon, 3 Nov 2008 09:27:38 +0100 [thread overview]
Message-ID: <20081103092738.35de1f08@surf> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909C2916C@mi8nycmail19.Mi8.com>
Le Fri, 31 Oct 2008 14:38:51 -0400,
"hartleys" <hartleys@visionengravers.com> a ?crit :
> I found the same issue back on 6/17/2008 and sent a patch on 7/7/2008
> that never got a response.
Argh, it's a shame to discover that people already faced the same
issues, sent patches, but that others end up re-debugging the issue
because the patches didn't get attention.
> Acked-by: H Hartley Sweeten <hsweeten@visionengravers.com>
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-11-03 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 9:02 [Buildroot] [PATCH] More external toolchain fixes Thomas Petazzoni
2008-10-31 13:18 ` Bernhard Reutner-Fischer
2008-10-31 18:38 ` hartleys
2008-11-03 8:27 ` Thomas Petazzoni [this message]
2008-11-03 10:20 ` Peter Korsgaard
2008-11-03 10:33 ` 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=20081103092738.35de1f08@surf \
--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