From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Alexander Aring <alex.aring@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] kconfig: Fix compiler warning
Date: Mon, 30 Jun 2014 08:03:29 +0200 [thread overview]
Message-ID: <20140630060329.GY14781@pengutronix.de> (raw)
In-Reply-To: <20140626090114.GA9064@omega>
On Thu, Jun 26, 2014 at 11:02:18AM +0200, Alexander Aring wrote:
> 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
There is also the macro uninitialized_var (in both kernel and barebox)
that could be used here instead of the explicit = NULL.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-06-30 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 6:13 Sascha Hauer
2014-06-26 9:02 ` Alexander Aring
2014-06-30 6:03 ` Uwe Kleine-König [this message]
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=20140630060329.GY14781@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
/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