From: Jonathan Marek <jonathan@marek.ca>
To: Arnd Bergmann <arnd@arndb.de>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: John Garry <john.garry@huawei.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Olof Johansson <olof@lixom.net>, SoC Team <soc@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH 0/2] arm64 defconfig: Get faddr2line working
Date: Thu, 28 Jul 2022 07:57:33 -0400 [thread overview]
Message-ID: <966a62da-52b6-1789-13d6-5fe06b62c7fe@marek.ca> (raw)
In-Reply-To: <CAK8P3a38uGGGLA4b2bi=v8cV6-dH5yEcvBYcwr5ChzkwMTX9_Q@mail.gmail.com>
On 7/28/22 5:09 AM, Arnd Bergmann wrote:
...
> diff --git a/drivers/soundwire/qcom.c b/drivers/soundwire/qcom.c
> index 22b706350ead..f65c7737c2db 100644
> --- a/drivers/soundwire/qcom.c
> +++ b/drivers/soundwire/qcom.c
> @@ -1289,11 +1289,7 @@ static int qcom_swrm_probe(struct platform_device *pdev)
> data = of_device_get_match_data(dev);
> ctrl->rows_index = sdw_find_row_index(data->default_rows);
> ctrl->cols_index = sdw_find_col_index(data->default_cols);
> -#if IS_REACHABLE(CONFIG_SLIMBUS)
> - if (dev->parent->bus == &slimbus_bus) {
> -#else
> - if (false) {
> -#endif
> + if (IS_ENABLED(CONFIG_SLIMBUS) && dev->parent->bus == &slimbus_bus) {
> ctrl->reg_read = qcom_swrm_ahb_reg_read;
> ctrl->reg_write = qcom_swrm_ahb_reg_write;
> ctrl->regmap = dev_get_regmap(dev->parent, NULL);
>
This relies on the compiler optimizing out the reference to slimbus_bus,
which doesn't exist in the CONFIG_SLIMBUS=n case (not tested, but I
think this means an O0 build will fail?).
next prev parent reply other threads:[~2022-07-28 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 16:43 John Garry
2022-07-24 16:43 ` [PATCH 1/2] arm64: defconfig: Sync with savedefconfig John Garry
2022-07-24 16:43 ` [PATCH 2/2] arm64: defconfig: Enable DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT John Garry
2022-07-24 20:35 ` [PATCH 0/2] arm64 defconfig: Get faddr2line working Arnd Bergmann
2022-07-25 6:50 ` John Garry
2022-07-25 7:08 ` Arnd Bergmann
2022-07-25 11:57 ` John Garry
2022-07-25 12:51 ` Arnd Bergmann
2022-07-25 14:03 ` John Garry
2022-07-25 14:22 ` Arnd Bergmann
2022-07-25 17:39 ` John Garry
2022-07-28 8:06 ` John Garry
2022-07-28 8:23 ` Arnd Bergmann
2022-07-28 8:53 ` Srinivas Kandagatla
2022-07-28 9:09 ` Arnd Bergmann
2022-07-28 11:57 ` Jonathan Marek [this message]
2022-07-28 12:03 ` Arnd Bergmann
2022-08-04 10:35 ` soundwire qcom slimbus dependency (was Re: [PATCH 0/2] arm64 defconfig: Get faddr2line working) John Garry
2022-08-09 8:28 ` John Garry
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=966a62da-52b6-1789-13d6-5fe06b62c7fe@marek.ca \
--to=jonathan@marek.ca \
--cc=arnd@arndb.de \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®