All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] infra/pkg-kconfig: Be sure to reconfigure the package on foo-reconfigure
Date: Fri, 16 Sep 2016 19:05:44 +0200	[thread overview]
Message-ID: <20160916190544.540efd8a@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LX0FwkjE8xHqjwn1TOS7cOdbVwjBRLOS7tLnKJcgBtDuQ@mail.gmail.com>

Hello,

On Wed, 14 Sep 2016 19:42:30 +0200, Thomas De Schampheleire wrote:

> I think the answer to this question is simple: one of the goals was to allow:
> 
> 'make clean linux-menuconfig'
> 
> without this step first building all dependencies of linux (which is
> quite a lot).
> If the kconfig configuration would be part of CONFIGURE_CMDS, then
> we'd end up in that situation.

Gaah, yes, indeed, makes sense. Can we write this somewhere?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2016-09-16 17:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 22:35 [Buildroot] [PATCH] infra/pkg-kconfig: Be sure to reconfigure the package on foo-reconfigure Yann E. MORIN
2016-09-13 22:59 ` Vivien Didelot
2016-09-13 23:29 ` Arnout Vandecappelle
2016-09-14  7:27 ` Thomas De Schampheleire
2016-09-14  9:01   ` Thomas Petazzoni
2016-09-14 17:42     ` Thomas De Schampheleire
2016-09-14 18:32       ` Yann E. MORIN
2016-09-14 18:38         ` Yann E. MORIN
2016-09-16 17:05       ` Thomas Petazzoni [this message]
2016-09-16 17:05 ` Thomas Petazzoni
2016-09-16 17:17   ` Yann E. MORIN
2016-09-16 17:56   ` Yann E. MORIN
2016-09-16 19:02   ` Yann E. MORIN
2016-09-17 12:42     ` Thomas Petazzoni
2016-09-17 12:53       ` Yann E. MORIN
2016-09-17 13:17         ` Thomas Petazzoni

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=20160916190544.540efd8a@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 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.