From: Vinod Koul <vkoul@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@kernel.org>,
linux-phy@lists.infradead.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] phy: ti: fix Kconfig warning and operator precedence
Date: Wed, 11 Jan 2023 13:25:09 +0530 [thread overview]
Message-ID: <Y75rXeTK7m/uAE9I@matsya> (raw)
In-Reply-To: <20230110062529.22668-1-rdunlap@infradead.org>
On 09-01-23, 22:25, Randy Dunlap wrote:
> Fix Kconfig depends operator precedence to prevent a Kconfig warning:
>
> WARNING: unmet direct dependencies detected for MUX_MMIO
> Depends on [n]: MULTIPLEXER [=m] && OF [=n]
> Selected by [m]:
> - PHY_AM654_SERDES [=m] && (OF [=n] && ARCH_K3 || COMPILE_TEST [=y]) && COMMON_CLK [=y]
>
> Fixes: 71e2f5c5c224 ("phy: ti: Add a new SERDES driver for TI's AM654x SoC")
> Fixes: 091876cc355d ("phy: ti: j721e-wiz: Add support for WIZ module present in TI J721E SoC")
>
Please no blank line here
Applied, after fixing this
--
~Vinod
prev parent reply other threads:[~2023-01-11 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 6:25 [PATCH] phy: ti: fix Kconfig warning and operator precedence Randy Dunlap
2023-01-11 7:55 ` Vinod Koul [this message]
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=Y75rXeTK7m/uAE9I@matsya \
--to=vkoul@kernel.org \
--cc=arnd@arndb.de \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=rdunlap@infradead.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