From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Add support for Alix2d3 board from PC Engines
Date: Fri, 6 Aug 2010 22:50:32 +0200 [thread overview]
Message-ID: <20100806225032.669dfa12@surf> (raw)
In-Reply-To: <4C5C5EB1.4020500@gmail.com>
Hello,
On Fri, 06 Aug 2010 22:12:49 +0300
Darius Augulis <augulis.darius@gmail.com> wrote:
> Did anybody review it? Maybe it's ready to merge it to main line?
As 2010.08-rc1 has been released, only bug fixes will be merged until
the release of 2010.08.
My top-priority item for 2010.11 is to cleanup the board support in
Buildroot (I already have a stack of patches started on this topic). As
part of this effort, I intend to merge all pending contributions that
add board support.
However, I don't consider this one as ready, as it adds a new complete
target skeleton for just a new Grub configuration, as discussed a week
ago on the list. We need to find a different solution to this than
duplicating the target skeleton.
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-08-06 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 20:48 [Buildroot] [PATCH 0/2] Add support for Alix2d3 board from PC Engines Darius Augulis
2010-07-12 20:48 ` [Buildroot] [PATCH 1/2] " Darius Augulis
2010-07-12 20:48 ` [Buildroot] [PATCH 2/2] Add target skeleton for Alix2d3 Darius Augulis
2010-07-13 6:53 ` Thomas Petazzoni
2010-07-20 18:13 ` Darius Augulis
2010-08-02 7:47 ` Thomas Petazzoni
2010-08-06 19:13 ` [Buildroot] [PATCH 0/2] Add support for Alix2d3 board from PC Engines Darius Augulis
2010-08-06 20:50 ` Thomas Petazzoni [this message]
2010-08-22 16:19 ` Darius Augulis
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=20100806225032.669dfa12@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