From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] infra/pkg-kconfig: Be sure to reconfigure the package on foo-reconfigure
Date: Sat, 17 Sep 2016 14:53:47 +0200 [thread overview]
Message-ID: <20160917125347.GA3613@free.fr> (raw)
In-Reply-To: <20160917144233.116fbc8a@free-electrons.com>
Thomas, All,
On 2016-09-17 14:42 +0200, Thomas Petazzoni spake thusly:
> On Fri, 16 Sep 2016 21:02:44 +0200, Yann E. MORIN wrote:
[--SNIP--]
> > So, I'd like to argue that this patch fixes the reported issue and covers
> > the use-case you pointed to.
>
> That was not the use-case I pointed to, what I pointed to what the
> following use-case:
>
> 1. Create a Buildroot configuration, with Linux enabled, using the
> omap2plus_defconfig
>
> 2. Build your system.
>
> 3. Go in menuconfig, and change the Linux defconfig to
> mvebu_v7_defconfig.
>
> 4. Run "make linux-reconfigure"
>
> I would expect the newly defined Linux configuration to be taken into
> account, but it's not, it only re-does the fixups and doesn't reload
> the configuration from mvebu_v7_defconfig.
Ah, I did not understand that. Indeed, this use-case is not covered,
neitehr currently nor with this patch applied.
However, I wonder how we could detect that condition...
> Now, we can discuss whether this is the behavior that we want or not.
> But at least, that's the behavior I was referring to, and which your
> patch doesn't address.
Indeed, that's not covered. But neither is it a regression...
> *But*, I'll apply your patch nonetheless because it fixes other issues,
> and doesn't change the behavior I'm describing.
Thanks!
I'll see if we can do something to cover your use-case...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-09-17 12:53 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
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 [this message]
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=20160917125347.GA3613@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox