From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Alex Elder <elder@linaro.org>
Cc: agross@kernel.org, ohad@wizery.com, davem@davemloft.net,
kuba@kernel.org, evgreen@chromium.org, cpratapa@codeaurora.org,
subashab@codeaurora.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] remoteproc: qcom: expose types for COMPILE_TEST
Date: Wed, 6 Jan 2021 12:47:08 -0600 [thread overview]
Message-ID: <X/YFrHDYAgyi619f@builder.lan> (raw)
In-Reply-To: <20210106023812.2542-2-elder@linaro.org>
On Tue 05 Jan 20:38 CST 2021, Alex Elder wrote:
> Stub functions are defined for SSR notifier registration in case
> QCOM_RPROC_COMMON is not configured. As a result, code that uses
> these functions can link successfully even if the common remoteproc
> code is not built.
>
> Code that registers an SSR notifier function likely needs the
> types defined in "qcom_rproc.h", but those are only exposed if
> QCOM_RPROC_COMMON is enabled.
>
> Rearrange the conditional definition so the qcom_ssr_notify_data
> structure and qcom_ssr_notify_type enumerated type are defined
> whether or not QCOM_RPROC_COMMON is enabled.
>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
@Jakub, @Dave, as this is a prerequisite for allowing IPA to be compile
tested feel free to merge it together with patch 3.
Regards,
Bjorn
> Signed-off-by: Alex Elder <elder@linaro.org>
> ---
> include/linux/remoteproc/qcom_rproc.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/remoteproc/qcom_rproc.h b/include/linux/remoteproc/qcom_rproc.h
> index 6470516621749..82b211518136e 100644
> --- a/include/linux/remoteproc/qcom_rproc.h
> +++ b/include/linux/remoteproc/qcom_rproc.h
> @@ -3,8 +3,6 @@
>
> struct notifier_block;
>
> -#if IS_ENABLED(CONFIG_QCOM_RPROC_COMMON)
> -
> /**
> * enum qcom_ssr_notify_type - Startup/Shutdown events related to a remoteproc
> * processor.
> @@ -26,6 +24,8 @@ struct qcom_ssr_notify_data {
> bool crashed;
> };
>
> +#if IS_ENABLED(CONFIG_QCOM_RPROC_COMMON)
> +
> void *qcom_register_ssr_notifier(const char *name, struct notifier_block *nb);
> int qcom_unregister_ssr_notifier(void *notify, struct notifier_block *nb);
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2021-01-06 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 2:38 [PATCH net-next 0/3] net: ipa: support COMPILE_TEST Alex Elder
2021-01-06 2:38 ` [PATCH net-next 1/3] remoteproc: qcom: expose types for COMPILE_TEST Alex Elder
2021-01-06 18:47 ` Bjorn Andersson [this message]
2021-01-06 2:38 ` [PATCH net-next 2/3] soc: qcom: mdt_loader: define stubs " Alex Elder
2021-01-06 18:47 ` Bjorn Andersson
2021-01-06 2:38 ` [PATCH net-next 3/3] net: ipa: support COMPILE_TEST Alex Elder
2021-01-06 7:34 ` kernel test robot
2021-01-06 19:43 ` Alex Elder
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=X/YFrHDYAgyi619f@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=subashab@codeaurora.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).