From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/autobuild v2 1/7] autobuild-run: fix typo in help text
Date: Wed, 12 Apr 2017 22:42:21 +0200 [thread overview]
Message-ID: <20170412224221.722494d6@free-electrons.com> (raw)
In-Reply-To: <20170410220003.30421-1-arnout@mind.be>
Hello,
On Mon, 10 Apr 2017 23:59:57 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> scripts/autobuild-run | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've applied patches 1 to 6. For patch 7, it needs to wait until I
apply the in-tree autobuild defconfigs.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-12 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 21:59 [Buildroot] [PATCH/autobuild v2 1/7] autobuild-run: fix typo in help text Arnout Vandecappelle
2017-04-10 21:59 ` [Buildroot] [PATCH/autobuild v2 2/7] autobuild-run: add '-d, --debug' option Arnout Vandecappelle
2017-04-10 21:59 ` [Buildroot] [PATCH/autobuild v2 3/7] autobuild-run: use 'olddefconfig' instead of 'oldconfig' Arnout Vandecappelle
2017-04-10 22:00 ` [Buildroot] [PATCH/autobuild v2 4/7] autobuild-run: check that toolchain config lines are still present Arnout Vandecappelle
2017-04-10 22:00 ` [Buildroot] [PATCH/autobuild v2 5/7] autobuild-run: remove check for glibc Arnout Vandecappelle
2017-04-10 22:00 ` [Buildroot] [PATCH/autobuild v2 6/7] autobuild-run: simplify, don't make a dict of config Arnout Vandecappelle
2017-04-12 20:42 ` Thomas Petazzoni
2017-04-13 20:41 ` Arnout Vandecappelle
2017-04-10 22:00 ` [Buildroot] [PATCH/autobuild v2 7/7] autobuild-run: use in-tree toolchain configs Arnout Vandecappelle
2017-04-12 20:42 ` Thomas Petazzoni [this message]
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=20170412224221.722494d6@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