From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] new package: atfirmware
Date: Fri, 13 May 2016 15:08:44 +0200 [thread overview]
Message-ID: <20160513150844.506a38ee@free-electrons.com> (raw)
In-Reply-To: <5735AA81.8010908@synopsys.com>
Hello,
On Fri, 13 May 2016 11:20:49 +0100, Joao Pinto wrote:
> Could you please check the patches?
Joao, I really do appreciate your patches, but it is definitely not
useful to ping every two days about them. There are currently 282
patches in the queue, so there's many many other patches than yours.
If you want to help, please review and/or test patches from others.
I'll get to your patches at some point (or someone else will), but this
may not happen in just two days.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-13 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 10:49 [Buildroot] [PATCH v2 0/2] new package: atfirmware Joao Pinto
2016-05-09 9:27 ` [Buildroot] [PATCH " Joao Pinto
[not found] ` <20160509225510.GA18182@e106497-lin.cambridge.arm.com>
2016-05-10 9:00 ` Joao Pinto
2016-05-13 10:20 ` Joao Pinto
2016-05-13 13:08 ` Thomas Petazzoni [this message]
2016-06-01 10:49 ` [Buildroot] [PATCH v2 1/2] new packages: atfirmware and scpfirmware Joao Pinto
2016-07-05 15:50 ` [Buildroot] [RESEND][PATCH " Maxime Hadjinlian
2016-06-01 10:49 ` [Buildroot] [PATCH v2 2/2] configs: add u-boot and atfirmware options to juno Joao Pinto
[not found] ` <20160601103734.GB23566@e106497-lin.cambridge.arm.com>
2016-06-01 10:45 ` [Buildroot] [RESEND] [PATCH 2/2] configs: add u-noot " Joao Pinto
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=20160513150844.506a38ee@free-electrons.com \
--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