| Message ID | 1372196264-3407-1-git-send-email-yann.morin.1998@free.fr (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Tue, Jun 25, 2013 at 11:37:44PM +0200, Yann E. MORIN wrote: > From: "Yann E. MORIN" <yann.morin.1998@free.fr> > > This reverts commit 8357b48549e17b3e4e402c7f977b65708922e60f. > > It breaks more stuff than it fixes. Thanks, I applied it to kbuild.git#kconfig, after verifying that the issue is gone. Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Michal, All, On 2013-06-26 15:48 +0200, Michal Marek spake thusly: > On Tue, Jun 25, 2013 at 11:37:44PM +0200, Yann E. MORIN wrote: > > From: "Yann E. MORIN" <yann.morin.1998@free.fr> > > > > This reverts commit 8357b48549e17b3e4e402c7f977b65708922e60f. > > > > It breaks more stuff than it fixes. > > Thanks, I applied it to kbuild.git#kconfig, after verifying that the > issue is gone. Yes, thanks. I'm sorry this second attempt was a (slightly different!) failure again. :-( The fix is working for boolean choices, but exposes a latent bug on tristate changes. Obviously, we must fix that latent bug first, but I can't come to a sane solution. I'll let it mature in a corner of my head for one more night. Maybe I'll see things clearer tomorrow. ;-) Regards, Yann E. MORIN.
On Wed, Jun 26, 2013 at 11:44 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote: > Michal, All, > > On 2013-06-26 15:48 +0200, Michal Marek spake thusly: >> On Tue, Jun 25, 2013 at 11:37:44PM +0200, Yann E. MORIN wrote: >> > From: "Yann E. MORIN" <yann.morin.1998@free.fr> >> > >> > This reverts commit 8357b48549e17b3e4e402c7f977b65708922e60f. >> > >> > It breaks more stuff than it fixes. >> >> Thanks, I applied it to kbuild.git#kconfig, after verifying that the >> issue is gone. > > Yes, thanks. I'm sorry this second attempt was a (slightly different!) > failure again. :-( > > The fix is working for boolean choices, but exposes a latent bug on > tristate changes. Obviously, we must fix that latent bug first, but I > can't come to a sane solution. > > I'll let it mature in a corner of my head for one more night. Maybe I'll > see things clearer tomorrow. ;-) > Just as a side-effect: Yesterday, I did some git-bisecting which has shown a char-misc-next issue. Unfortunately, I had to revert this change in several runs to do a sane bisecting. NOTE: Can you please write up some cooler changelog next time why this revert was done? In one of your emails you did some nice analysis. Such informations belong IMHO into the revert's changelog. - Sedat - > 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. | > '------------------------------^-------^------------------^--------------------' -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Sedat, All, On 2013-06-27 08:23 +0200, Sedat Dilek spake thusly: > On Wed, Jun 26, 2013 at 11:44 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote: > > Michal, All, > > > > On 2013-06-26 15:48 +0200, Michal Marek spake thusly: > >> On Tue, Jun 25, 2013 at 11:37:44PM +0200, Yann E. MORIN wrote: > >> > From: "Yann E. MORIN" <yann.morin.1998@free.fr> > >> > > >> > This reverts commit 8357b48549e17b3e4e402c7f977b65708922e60f. > >> > > >> > It breaks more stuff than it fixes. > >> > >> Thanks, I applied it to kbuild.git#kconfig, after verifying that the > >> issue is gone. > > > > Yes, thanks. I'm sorry this second attempt was a (slightly different!) > > failure again. :-( [--SNIP--] > Can you please write up some cooler changelog next time why this > revert was done? > In one of your emails you did some nice analysis. > Such informations belong IMHO into the revert's changelog. Yes, you are right, I'll do next time I'll have to send a revert patch (which I hope not to have to for some time! ;-) ) Regards, Yann E. MORIN.
diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c index 3e39208..c55c227 100644 --- a/scripts/kconfig/confdata.c +++ b/scripts/kconfig/confdata.c @@ -288,6 +288,8 @@ load: for_all_symbols(i, sym) { sym->flags |= SYMBOL_CHANGED; sym->flags &= ~(def_flags|SYMBOL_VALID); + if (sym_is_choice(sym)) + sym->flags |= def_flags; switch (sym->type) { case S_INT: case S_HEX: @@ -377,13 +379,13 @@ setsym: case mod: if (cs->def[def].tri == yes) { conf_warning("%s creates inconsistent choice state", sym->name); + cs->flags &= ~def_flags; } break; case yes: if (cs->def[def].tri != no) conf_warning("override: %s changes choice state", sym->name); cs->def[def].val = sym; - cs->flags |= def_flags; break; } cs->def[def].tri = EXPR_OR(cs->def[def].tri, sym->def[def].tri); @@ -789,8 +791,6 @@ int conf_write(const char *name) sym_calc_value(sym); if (!(sym->flags & SYMBOL_WRITE)) goto next; - if (sym_is_choice_value(sym) && !menu_is_visible(menu->parent)) - goto next; sym->flags &= ~SYMBOL_WRITE; conf_write_symbol(out, sym, &kconfig_printer_cb, NULL);