From: Rong Chen <rong.a.chen@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [kbuild-all] Re: sound/soc/soc-compress.c:75:28: warning: 'component' is used uninitialized in this function
Date: Wed, 22 Apr 2020 15:39:25 +0800 [thread overview]
Message-ID: <7048e026-2f6c-7b49-000a-a3b313a14366@intel.com> (raw)
In-Reply-To: <875zdsunmj.wl-kuninori.morimoto.gx@renesas.com>
On 4/22/20 12:53 PM, Kuninori Morimoto wrote:
> Hi Rong
>
>>> Hmm... I still can't reproduce this issue.
>>> I don't have gcc-6, thus can't try it.
>>> Is this the issue ??
> (snip)
>> We can reproduce the warning with gcc-6 (gcc version 6.5.0 20181026
>> (Debian 6.5.0-2)),
>> and the warning can be closed if changed to "struct snd_soc_component
>> *component = NULL, *save = NULL;"
> Thank you for your feedback.
> It sounds reasonable for me.
> Can you post it ? or do you want me to do it ?
Thanks, I have posted it.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2020-04-22 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:53 kbuild test robot
2020-04-21 6:23 ` Kuninori Morimoto
2020-04-22 1:17 ` [kbuild-all] " Rong Chen
2020-04-22 4:53 ` Kuninori Morimoto
2020-04-22 7:39 ` Rong Chen [this message]
2020-04-22 7:35 ` [PATCH] ASoC: soc-compress: avoid false-positive Wuninitialized warning Rong Chen
2020-04-22 22:18 ` Kuninori Morimoto
2020-04-23 13:49 ` Mark Brown
2020-04-24 12:19 ` Mark Brown
2020-04-24 0:54 ` [PATCH v2] " Rong Chen
2020-04-24 4:34 ` Kuninori Morimoto
2020-04-24 12:19 ` Mark Brown
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=7048e026-2f6c-7b49-000a-a3b313a14366@intel.com \
--to=rong.a.chen@intel.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®