From: Masahiro Yamada <masahiroy@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Brown <broonie@kernel.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
mhocko@suse.cz, mm-commits@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
moderated for non-subscribers <alsa-devel@alsa-project.org>
Subject: Re: mmotm 2020-03-11-21-11 uploaded (sound/soc/codecs/wcd9335.c)
Date: Fri, 13 Mar 2020 13:52:46 +0900 [thread overview]
Message-ID: <CAK7LNARaR9_GPE+uU9Fh73850dwJXKETyF4gJxats_hrhgwzAg@mail.gmail.com> (raw)
In-Reply-To: <a8343b1f-7e87-d34d-a71b-86d20a8a3aff@linaro.org>
On Fri, Mar 13, 2020 at 1:59 AM Srinivas Kandagatla
<srinivas.kandagatla@linaro.org> wrote:
>
> Adding+ Masahiro Yamada for more inputs w.r.t kconfig.
>
>
> Kconfig side we have:
>
> config SND_SOC_ALL_CODECS
> tristate "Build all ASoC CODEC drivers"
> imply SND_SOC_WCD9335
>
> config SND_SOC_WCD9335
> tristate "WCD9335 Codec"
> depends on SLIMBUS
> ...
>
> The implied symbol SND_SOC_WCD9335 should be set based on direct
> dependency, However in this case, direct dependency SLIMBUS=m where as
> SND_SOC_WCD9335=y. I would have expected to be SND_SOC_WCD9335=m in this
> case.
>
> Is this a valid possible case or a bug in Kconfig?
>
The patch exist:
https://patchwork.kernel.org/patch/11414795/
However, this caused another problem, then
got reverted in linux-next.
It fixed it too, so hopefully
this will be solved soon.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2020-03-13 4:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 6:27 incoming Andrew Morton
2020-03-06 6:28 ` [patch 1/7] mm, numa: fix bad pmd by atomically check for pmd_trans_huge when marking page tables prot_numa Andrew Morton
2020-03-06 6:28 ` [patch 2/7] mm: fix possible PMD dirty bit lost in set_pmd_migration_entry() Andrew Morton
2020-03-06 6:28 ` [patch 3/7] mm: avoid data corruption on CoW fault into PFN-mapped VMA Andrew Morton
2020-03-06 6:28 ` [patch 4/7] fat: fix uninit-memory access for partial initialized inode Andrew Morton
2020-03-06 6:28 ` [patch 5/7] mm/z3fold.c: do not include rwlock.h directly Andrew Morton
2020-03-06 6:28 ` [patch 6/7] mm, hotplug: fix page online with DEBUG_PAGEALLOC compiled but not enabled Andrew Morton
2020-03-06 6:28 ` [patch 7/7] arch/Kconfig: update HAVE_RELIABLE_STACKTRACE description Andrew Morton
2020-03-12 4:12 ` mmotm 2020-03-11-21-11 uploaded Andrew Morton
2020-03-12 15:03 ` mmotm 2020-03-11-21-11 uploaded (sound/soc/codecs/wcd9335.c) Randy Dunlap
2020-03-12 16:59 ` Srinivas Kandagatla
2020-03-13 4:52 ` Masahiro Yamada [this message]
2020-03-13 4:49 ` mmotm 2020-03-12-21-49 uploaded Andrew Morton
2020-03-21 22:17 ` mmotm 2020-03-21-15-17 uploaded Andrew Morton
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=CAK7LNARaR9_GPE+uU9Fh73850dwJXKETyF4gJxats_hrhgwzAg@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=srinivas.kandagatla@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).