From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vaishali Thakkar <vaishali.thakkar@linaro.org>
Cc: andy.gross@linaro.org, david.brown@linaro.org,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
vkoul@kernel.org
Subject: Re: [PATCH v4 2/5] base: soc: Export soc_device_register/unregister APIs
Date: Fri, 1 Mar 2019 11:08:42 -0800 [thread overview]
Message-ID: <20190301190842.GB27005@builder> (raw)
In-Reply-To: <20190225065044.11023-3-vaishali.thakkar@linaro.org>
On Sun 24 Feb 22:50 PST 2019, Vaishali Thakkar wrote:
> From: Vinod Koul <vkoul@kernel.org>
>
> Qcom Socinfo driver can be built as a module, so
> export these two APIs.
>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> Signed-off-by: Vaishali Thakkar <vaishali.thakkar@linaro.org>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> ---
> Changes since v3:
> - Add Greg's reviewed-by
> Changes since v2:
> - Reorder patches [patch 5->patch 2]
> Changes since v1:
> - None
> ---
> drivers/base/soc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/base/soc.c b/drivers/base/soc.c
> index b0933b9fe67f..7c0c5ca5953d 100644
> --- a/drivers/base/soc.c
> +++ b/drivers/base/soc.c
> @@ -164,6 +164,7 @@ struct soc_device *soc_device_register(struct soc_device_attribute *soc_dev_attr
> out1:
> return ERR_PTR(ret);
> }
> +EXPORT_SYMBOL_GPL(soc_device_register);
>
> /* Ensure soc_dev->attr is freed prior to calling soc_device_unregister. */
> void soc_device_unregister(struct soc_device *soc_dev)
> @@ -173,6 +174,7 @@ void soc_device_unregister(struct soc_device *soc_dev)
> device_unregister(&soc_dev->dev);
> early_soc_dev_attr = NULL;
> }
> +EXPORT_SYMBOL_GPL(soc_device_unregister);
>
> static int __init soc_bus_register(void)
> {
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-03-01 19:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 6:50 [PATCH v4 0/5] soc: qcom: Add SoC info driver Vaishali Thakkar
2019-02-25 6:50 ` [PATCH v4 1/5] base: soc: Add serial_number attribute to soc Vaishali Thakkar
2019-02-28 19:23 ` Stephen Boyd
2019-02-25 6:50 ` [PATCH v4 2/5] base: soc: Export soc_device_register/unregister APIs Vaishali Thakkar
2019-02-28 19:23 ` Stephen Boyd
2019-03-01 19:08 ` Bjorn Andersson [this message]
2019-02-25 6:50 ` [PATCH v4 3/5] soc: qcom: Add socinfo driver Vaishali Thakkar
2019-02-28 19:34 ` Stephen Boyd
2019-03-01 19:23 ` Bjorn Andersson
2019-02-25 6:50 ` [PATCH v4 4/5] soc: qcom: socinfo: Expose custom attributes Vaishali Thakkar
2019-02-28 21:32 ` Stephen Boyd
2019-03-14 11:25 ` Vaishali Thakkar
2019-03-14 15:58 ` Stephen Boyd
2019-03-21 5:51 ` Vaishali Thakkar
2019-03-23 0:01 ` Stephen Boyd
2019-03-24 17:42 ` Vaishali Thakkar
2019-03-25 16:01 ` Stephen Boyd
2019-03-25 20:58 ` Vaishali Thakkar
2019-03-01 19:42 ` Bjorn Andersson
2019-02-25 6:50 ` [PATCH v4 5/5] soc: qcom: socinfo: Expose image information Vaishali Thakkar
2019-02-28 21:34 ` Stephen Boyd
2019-03-01 19:51 ` Bjorn Andersson
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=20190301190842.GB27005@builder \
--to=bjorn.andersson@linaro.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=vaishali.thakkar@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