On Fri, Feb 6, 2015 at 4:50 PM, Greg Kroah-Hartman
<gre...@linuxfoundation.org> wrote:
> 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.
>

commit 2d560306096739e2251329ab5c16059311a151b0
kconfig: Fix warning "‘jump’ may be used uninitialized"

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to