From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] kconfig: Fix compiler warning
Date: Thu, 26 Jun 2014 11:02:18 +0200 [thread overview]
Message-ID: <20140626090114.GA9064@omega> (raw)
In-Reply-To: <1403763212-924-1-git-send-email-s.hauer@pengutronix.de>
Hi Sascha,
I get this warning about 1 month and it makes me crazy and I am unsing
"gcc (GCC) 4.9.0 20140604 (prerelease)".
Why I didn't sent any patches?
Because you say it here it's a compiler bug and the linux world doesn't
fix it this way. Look at [0].
"... since we will still want to catch unitialised use in the future,
should we were to changethe code." - which sounds useful.
They already add a comment to this. I think otherwise they get much
patches because this warning.
When I look into the current mainline code [1]. Then this is currently
not fixed in any way (comment or setting to NULL
- Alex
[0] http://www.spinics.net/lists/linux-kbuild/msg08898.html
[1] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/kconfig/menu.c?id=refs/tags/next-20140626
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-26 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 6:13 [PATCH] kconfig: Fix compiler warning Sascha Hauer
2014-06-26 9:02 ` Alexander Aring [this message]
2014-06-30 6:03 ` Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2014-11-20 5:44 Eddie Kovsky
2014-11-28 13:19 ` Michal Marek
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=20140626090114.GA9064@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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.