From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sedat Dilek <sedat.dilek@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Michal Marek <mmarek@suse.cz>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: [pull request] Pull request for branch yem-kconfig-for-next
Date: Sat, 27 Apr 2013 00:17:59 +0200 [thread overview]
Message-ID: <cover.1367014328.git.yann.morin.1998@free.fr> (raw)
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Michal,
Please pull this to revert:
422c809: fix randomising choice entries in presence of KCONFIG_ALLCONFIG
It causes more harm that it fixes issues, and I couldn't find a proper
fix for now. To avoid breakage so close to the opening of the merge
window, it makes more sense to revert it than to wait for a fix.
As I already said earlier, I'll be on vacation the next two weeks, so
I should find some time to look back at this again, hopefully before
-rc1 is out (but any sane person that value his/her life should not hold
his/her breath...)
The following changes since commit e43956e607692f9b1c710311e4a6591ffba1edf0:
kconfig: implement KCONFIG_PROBABILITY for randconfig (2013-04-25 00:16:30 +0200)
are available in the git repository at:
git://gitorious.org/linux-kconfig/linux-kconfig.git yem-kconfig-for-next
for you to fetch changes up to 23a5dfdad22a574d19d7cc19b391f9ce0d3c2f21:
Revert "kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG" (2013-04-26 23:21:59 +0200)
----------------------------------------------------------------
Yann E. MORIN (1):
Revert "kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG"
scripts/kconfig/confdata.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
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 reply other threads:[~2013-04-26 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 22:17 Yann E. MORIN [this message]
2013-04-26 22:18 ` [PATCH 1/1] Revert "kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG" Yann E. MORIN
2013-04-29 12:09 ` [pull request] Pull request for branch yem-kconfig-for-next Michal Marek
-- strict thread matches above, loose matches on Subject: below --
2013-04-29 17:59 Yann E. MORIN
2013-05-02 8:48 ` Michal Marek
2013-06-18 22:44 Yann E. MORIN
2013-06-19 20:40 ` Michal Marek
2013-06-19 21:01 ` Yann E. MORIN
2013-06-29 14:21 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=cover.1367014328.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sedat.dilek@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).