From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] rpi-firmware: Fixup config.txt
Date: Mon, 29 Apr 2013 22:23:27 +0200 [thread overview]
Message-ID: <517ED6BF.1030304@mind.be> (raw)
In-Reply-To: <517E2FEB.2080009@synopsys.com>
On 29/04/13 10:31, Alexey Brodkin wrote:
> Seems like this patch has never been even reviewed since last January.
> Even though it helps to use buildroot-built projects on RPi.
>
> Is there a chance to get it reviewed/accepted?
>
> Or is it supposed to be re-sent together with modifications in "[PATCH
> 2/2] configs: add RaspberryPi defconfig"?
Hi Alexey,
Feel free to test these patches and add your
Tested-by: ...
tag. Or to review them and add an Acked-by.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-04-29 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 14:23 [Buildroot] [PATCH 1/2] rpi-firmware: Fixup config.txt Maxime Hadjinlian
2013-01-13 14:23 ` [Buildroot] [PATCH 2/2] configs: add RaspberryPi defconfig Maxime Hadjinlian
2013-01-13 16:17 ` Samuel Martin
2013-03-22 12:06 ` Maxime Hadjinlian
2013-03-22 12:58 ` Thomas Petazzoni
2013-03-22 23:04 ` [Buildroot] [PATCH] " Maxime Hadjinlian
2013-03-25 4:33 ` [Buildroot] [PATCH 2/2] " Vivien Didelot
2013-03-22 12:05 ` [Buildroot] [PATCH 1/2] rpi-firmware: Fixup config.txt Maxime Hadjinlian
2013-04-29 8:31 ` Alexey Brodkin
2013-04-29 20:23 ` Arnout Vandecappelle [this message]
2013-04-29 20:48 ` Thomas Petazzoni
2013-04-29 22:00 ` Maxime Hadjinlian
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=517ED6BF.1030304@mind.be \
--to=arnout@mind.be \
--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