From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] List of pending patches: what to do?
Date: Thu, 1 Aug 2013 09:41:19 +0200 [thread overview]
Message-ID: <20130801094119.521a0cbd@skate> (raw)
In-Reply-To: <CAHt8ZCMACE5Y3QTH+_o-y5CMCcPjOsOEcTYETLx0RgaHRYaMJg@mail.gmail.com>
Dear Simon Dawson,
On Thu, 1 Aug 2013 07:54:33 +0100, Simon Dawson wrote:
> On 31 July 2013 18:14, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > http://patchwork.ozlabs.org/patch/165674 [RFC,1/2] Add configuration item for custom JavaScript install path
> > http://patchwork.ozlabs.org/patch/165675 [RFC,2/2] Use JavaScript install path from configuration during package installation
>
> These can be discarded now, as I have no intention of working on them further.
Thanks, done.
> > http://patchwork.ozlabs.org/patch/213384 [RFC] Fix avr32 build using internal toolchain
>
> No longer relevant, as uClibc 0.9.31 support has now been removed from
> Buildroot. Can be discarded.
Done.
> > http://patchwork.ozlabs.org/patch/236409 udev: fix avr32 and microblaze build failures
>
> I haven't noticed any avr32/microblaze udev autobuild failures for a
> while... I suggest that this patch be discarded.
Most likely we have upgraded the avr32 and microblaze toolchains since
then, and that's why we're not seeing the issues anymore. I've
discarded the patch.
> > http://patchwork.ozlabs.org/patch/238366 [RFC] permit menu customization
>
> This doesn't adequately solve the problem that it sets out to solve;
> can be discarded. (Although I do think this is still an area in which
> Buildroot could be improved.)
I agree it's an area in which Buildroot could be improved. I've dropped
the patch for now, as you suggested.
Thanks for this review!
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:[~2013-08-01 7:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 17:14 [Buildroot] List of pending patches: what to do? Thomas Petazzoni
2013-07-31 17:18 ` Thomas Petazzoni
2013-07-31 20:44 ` Yann E. MORIN
2013-08-01 5:39 ` Thomas Petazzoni
2013-07-31 17:51 ` Gustavo Zacarias
2013-08-01 5:50 ` Thomas Petazzoni
2013-07-31 20:45 ` Thomas De Schampheleire
2013-07-31 20:57 ` Yann E. MORIN
2013-08-01 5:59 ` Thomas Petazzoni
2013-08-01 20:24 ` Yann E. MORIN
2013-07-31 20:55 ` Yann E. MORIN
2013-08-01 6:04 ` Thomas Petazzoni
2013-07-31 22:13 ` Samuel Martin
2013-07-31 22:20 ` Yann E. MORIN
2013-08-01 16:23 ` Thomas Petazzoni
2013-08-01 21:30 ` Samuel Martin
2013-08-02 8:33 ` Thomas De Schampheleire
2013-08-02 8:50 ` Thomas Petazzoni
2013-08-02 9:09 ` Thomas De Schampheleire
2013-08-02 9:10 ` Thomas Petazzoni
2013-08-02 9:27 ` Thomas De Schampheleire
2013-08-12 21:01 ` Arnout Vandecappelle
2013-08-01 2:52 ` Danomi Manchego
2013-08-01 6:13 ` Thomas Petazzoni
2013-08-01 20:14 ` Yann E. MORIN
2013-08-01 6:54 ` Simon Dawson
2013-08-01 7:41 ` Thomas Petazzoni [this message]
2013-08-01 16:16 ` Thomas Petazzoni
2013-08-02 8:10 ` Jérôme Pouiller
2013-08-02 11:11 ` Patrick Ziegler
2013-08-02 11:17 ` Thomas Petazzoni
2013-08-19 10:35 ` Luca Ceresoli
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=20130801094119.521a0cbd@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