From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [next] test_rust: use standard defconfig fragment style
Date: Tue, 20 Nov 2018 09:01:34 +0100 [thread overview]
Message-ID: <20181120090134.477ce99e@windsurf.home> (raw)
In-Reply-To: <20181116222147.13887-1-ricardo.martincoski@gmail.com>
Hello,
On Fri, 16 Nov 2018 20:21:47 -0200, Ricardo Martincoski wrote:
> Since commit "2927f412be support/testing: standardize defconfig
> fragments style" all other test cases use the same style for defconfig
> fragments:
> - start after a backslash;
> - be declared as a multi-line string literal;
> - be indented one level more than the variable that contains it.
>
> Do the same here for consistency.
>
> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> Cc: Matt Weber <matthew.weber@rockwellcollins.com>
> ---
> support/testing/tests/package/test_rust.py | 78 +++++++++++-----------
> 1 file changed, 39 insertions(+), 39 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-11-20 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 22:21 [Buildroot] [next] test_rust: use standard defconfig fragment style Ricardo Martincoski
2018-11-17 1:19 ` Matthew Weber
2018-11-20 8:01 ` 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=20181120090134.477ce99e@windsurf.home \
--to=thomas.petazzoni@bootlin.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