From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: kernel test robot <lkp@intel.com>, Daniel Baluta <daniel.baluta@nxp.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: sound/soc/sof/sof-audio.c:375 sof_machine_check() warn: inconsistent indenting
Date: Mon, 19 Oct 2020 09:36:11 -0500 [thread overview]
Message-ID: <d4eb5888-1a9e-60c3-d01f-5601b559741f@linux.intel.com> (raw)
In-Reply-To: <202010190917.V19qtBGc-lkp@intel.com>
On 10/18/20 8:41 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 7cf726a59435301046250c42131554d9ccc566b8
> commit: 285880a23d105e5d34b311b0c44061dffb07e405 ASoC: SOF: Make creation of machine device from SOF core optional
> date: 10 months ago
> config: i386-randconfig-m021-20201019 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> smatch warnings:
> sound/soc/sof/sof-audio.c:375 sof_machine_check() warn: inconsistent indenting
> sound/soc/sof/sof-audio.c:380 sof_machine_check() warn: ignoring unreachable code.
we provided a fix for this:
[PATCH 3/4] ASoC: SOF: sof-audio: remove goto used for force-nocodec support
but I don't see it in Mark's tree. That was part of the series
"[PATCH 0/4] ASoC: SOF: cleanups for 5.10" shared by Kai Vehmanen on
September 30.
I don't recall what happened with this series?
next prev parent reply other threads:[~2020-10-19 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 1:41 kernel test robot
2020-10-19 14:36 ` Pierre-Louis Bossart [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-18 1:50 kernel test robot
2020-09-18 16:34 ` Pierre-Louis Bossart
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=d4eb5888-1a9e-60c3-d01f-5601b559741f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ranjani.sridharan@linux.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
Powered by JetHome