All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] support/scripts: add check-dotconfig.py
Date: Mon, 20 Apr 2020 14:38:23 +0200	[thread overview]
Message-ID: <20200420143823.3883eaba@windsurf.home> (raw)
In-Reply-To: <ec5face2-dba6-695a-81f4-1b4948261720@gmail.com>

On Mon, 20 Apr 2020 14:19:55 +0200
Romain Naour <romain.naour@gmail.com> wrote:

> Not with the current implementation of the runtime-test infrastructure since the
> defconfig is bundled in the test python script.
> 
> The defconfig is written to .config but then we run make olddefconfig to
> generate the real .config. So we can't compare the .config file with
> check-dotconfig.py without creating a defconfig file.

Well, we can always have the defconfig written to a different file,
then copied to .config, that's not a big change to introduce.

> This can be easily be done in a followup patch.

Excellent, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-20 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  9:17 [Buildroot] [PATCH 1/2] support/scripts: add check-dotconfig.py Romain Naour
2020-04-20  9:17 ` [Buildroot] [PATCH 2/2] gitlab-ci: check generated config files Romain Naour
2020-04-20 11:52 ` [Buildroot] [PATCH 1/2] support/scripts: add check-dotconfig.py Thomas Petazzoni
2020-04-20 12:19   ` Romain Naour
2020-04-20 12:38     ` Thomas Petazzoni [this message]
2020-04-20 13:06 ` Yann E. MORIN

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=20200420143823.3883eaba@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 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.