From: Takashi Iwai <tiwai@suse.de>
To: Xingyu Wu <xingyu.wu@starfivetech.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Claudiu Beznea <Claudiu.Beznea@microchip.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Maxim Kochetkov <fido_max@inbox.ru>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Walker Chen <walker.chen@starfivetech.com>,
<linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v1] ASoC: dwc: Fix the warnnings about JH7110 ops
Date: Tue, 29 Aug 2023 08:40:02 +0200 [thread overview]
Message-ID: <877cpewdvh.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230829033658.225713-1-xingyu.wu@starfivetech.com>
On Tue, 29 Aug 2023 05:36:58 +0200,
Xingyu Wu wrote:
>
> Add a check of CONFIG_OF before the JH7110 ops to fix the warnings
> that the JH7110 ops are defined but not used when CONFIG_OF is disabled.
>
> Fixes: 1a512d13837a ("Add I2S support for the StarFive JH7110 SoC")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202308250433.nhzrhYEo-lkp@intel.com/
> Signed-off-by: Xingyu Wu <xingyu.wu@starfivetech.com>
> ---
> Hi Mark,
>
> This patch fixes the issue about the warning of JH7110 ops when CONFIG_OF
> is disabled. So add a check of CONFIG_OF before defining JH7110 ops.
>
> Thanks,
> Xingyu Wu
The very same fix went already in my sound.git tree, commit
8d2a0cdf5229.
thanks,
Takashi
next prev parent reply other threads:[~2023-08-29 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 3:36 [PATCH v1] ASoC: dwc: Fix the warnnings about JH7110 ops Xingyu Wu
2023-08-29 6:40 ` Takashi Iwai [this message]
2023-08-29 6:59 ` Xingyu Wu
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=877cpewdvh.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Claudiu.Beznea@microchip.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fido_max@inbox.ru \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=walker.chen@starfivetech.com \
--cc=xingyu.wu@starfivetech.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