From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] lsof: stop overriding CFLAGS in build
Date: Thu, 4 Nov 2010 20:35:05 +0100 [thread overview]
Message-ID: <20101104203505.65c0c12e@surf> (raw)
In-Reply-To: <BLU0-SMTP1368DBCA5159307B5213EDFE74B0@phx.gbl>
On Thu, 4 Nov 2010 18:09:59 +0100
Andy Gibbs <andyg1001@hotmail.co.uk> wrote:
> I wasn't able to find the patch you reference, but I downloaded 4.84 and
> scanning over it quickly, I believe the patch just committed is still
> required. If you can point me to the patch bumping to 4.84, then I will do
> some testing, if you wish.
http://lists.busybox.net/pipermail/buildroot/2010-October/038111.html
If you can test and report, that would be great.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-11-04 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 16:15 [Buildroot] [git commit master 1/1] lsof: stop overriding CFLAGS in build Peter Korsgaard
2010-11-04 16:39 ` Thomas Petazzoni
2010-11-04 17:09 ` Andy Gibbs
2010-11-04 19:35 ` Thomas Petazzoni [this message]
2010-11-05 13:10 ` Andy Gibbs
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=20101104203505.65c0c12e@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