All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7 v4] support/test-pkg: fixes and enhancements
Date: Sun, 12 Feb 2017 15:53:07 +0100	[thread overview]
Message-ID: <cover.1486911180.git.yann.morin.1998@free.fr> (raw)

Hello All!

This series brins a few fixes and improvements to the test-pkg script.

First, it fixes the cioding style, to be more in-line with what is used
in Buildroot.

Changes v2 -> v3:
  - drop patches already applied
  - simplify the config check  (Cam)
  - be less verbose  (Thomas)
  - fix coding style  (Thomas)

Changes v2 -> v3:
  - simplify the code to store missing config lines  (Luca)
  - properly run when -r is not provided
  - add 5th path to use an alternate list
  - add 6th patch to print the progress [n/N] for each toolchain


Regards,
Yann E. MORIN.


The following changes since commit 8ac3f121f0ccc31a79b08c473e19e4d4ae922942

  wiringpi: fix static linking (2017-02-12 15:03:02 +0100)


are available in the git repository at:

  git://git.buildroot.org/~ymorin/git/buildroot.git

for you to fetch changes up to 05e8a8e4a66b175edcd8f6250c583051f77eeae9

  support/test-pkg: print number of toolchain and progress (2017-02-12 15:18:08 +0100)


----------------------------------------------------------------
Yann E. MORIN (7):
      supprt/test-pkg: fix code style
      support/scripts: check the config snippet exists
      support/test-pkg: simplify the config check
      support/test-pkg: be less verbose
      support/test-pkg: report number and types of failures
      support/test-pkg: add option to use an alternate list of toolchains
      support/test-pkg: print number of toolchain and progress

 support/scripts/test-pkg | 125 ++++++++++++++++++++++++++++++-----------------
 1 file changed, 81 insertions(+), 44 deletions(-)

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

             reply	other threads:[~2017-02-12 14:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 14:53 Yann E. MORIN [this message]
2017-02-12 14:53 ` [Buildroot] [PATCH 1/7 v4] supprt/test-pkg: fix code style Yann E. MORIN
2017-02-12 15:02   ` Thomas Petazzoni
2017-02-12 14:53 ` [Buildroot] [PATCH 2/7 v4] support/scripts: check the config snippet exists Yann E. MORIN
2017-02-12 15:02   ` Thomas Petazzoni
2017-02-12 14:53 ` [Buildroot] [PATCH 3/7 v4] support/test-pkg: simplify the config check Yann E. MORIN
2017-02-12 15:02   ` Thomas Petazzoni
2017-02-12 14:53 ` [Buildroot] [PATCH 4/7 v4] support/test-pkg: be less verbose Yann E. MORIN
2017-02-12 15:02   ` Thomas Petazzoni
2017-02-12 14:53 ` [Buildroot] [PATCH 5/7 v4] support/test-pkg: report number and types of failures Yann E. MORIN
2017-02-12 15:02   ` Thomas Petazzoni
2017-02-12 14:53 ` [Buildroot] [PATCH 6/7 v4] support/test-pkg: add option to use an alternate list of toolchains Yann E. MORIN
2017-02-12 14:53 ` [Buildroot] [PATCH 7/7 v4] support/test-pkg: print number of toolchain and progress Yann E. MORIN
2017-02-15 21:44 [Buildroot] [PATCH 0/7 v4] support/test-pkg: fixes and enhancements Yann E. MORIN
2017-04-05 14:37 ` Arnout Vandecappelle
2017-04-05 19:16   ` Yann E. MORIN
2017-04-06  8:48     ` Arnout Vandecappelle
2017-04-06 15:55       ` Yann E. MORIN
2017-04-06 17:19         ` Arnout Vandecappelle

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=cover.1486911180.git.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.