From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: "Peter Kümmel" <syntheticpp@gmx.net>,
"Michal Marek" <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-3.18.y: Add "kconfig: Fix warning "‘jump’ may be used uninitialized""
Date: Fri, 6 Feb 2015 07:50:09 -0800 [thread overview]
Message-ID: <20150206155009.GA23394@kroah.com> (raw)
In-Reply-To: <CA+icZUWoPxGgzgjiMEJ1PPXjRp_oa8_C0tceTyK4Ao6_Hco+Gw@mail.gmail.com>
On Fri, Feb 06, 2015 at 04:40:28PM +0100, Sedat Dilek wrote:
> Hi,
>
> I see the following...
>
> $ yes "" | make oldconfig && make silentoldconfig </dev/null
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/kconfig/conf.o
> SHIPPED scripts/kconfig/zconf.tab.c
> SHIPPED scripts/kconfig/zconf.lex.c
> SHIPPED scripts/kconfig/zconf.hash.c
> HOSTCC scripts/kconfig/zconf.tab.o
> In file included from scripts/kconfig/zconf.tab.c:2537:0:
> scripts/kconfig/menu.c: In function ‘get_symbol_str’:
> scripts/kconfig/menu.c:590:18: warning: ‘jump’ may be used
> uninitialized in this function [-Wmaybe-uninitialized]
> jump->offset = strlen(r->s);
> ^
> scripts/kconfig/menu.c:551:19: note: ‘jump’ was declared here
> struct jump_key *jump;
> ^
> HOSTLD scripts/kconfig/conf
> scripts/kconfig/conf --oldconfig Kconfig
> #
> # configuration written to .config
> #
> scripts/kconfig/conf --silentoldconfig Kconfig
>
> The fix is "kconfig: Fix warning "‘jump’ may be used uninitialized"" upstream.
Sure, what's the git commit id of the patch in Linus's tree? That's
annoying to me as well, thanks for reminding me about it.
greg k-h
next prev parent reply other threads:[~2015-02-06 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 15:40 linux-3.18.y: Add "kconfig: Fix warning "‘jump’ may be used uninitialized"" Sedat Dilek
2015-02-06 15:50 ` Greg Kroah-Hartman [this message]
2015-02-06 16:22 ` Sedat Dilek
2015-03-04 6:44 ` Sedat Dilek
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=20150206155009.GA23394@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sedat.dilek@gmail.com \
--cc=syntheticpp@gmx.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 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.