From: Johan Hovold <johan+linaro@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
stable@vger.kernel.org
Subject: [PATCH 1/2] mfd: pm8008: fix module autoloading
Date: Fri, 26 May 2023 11:16:45 +0200 [thread overview]
Message-ID: <20230526091646.17318-2-johan+linaro@kernel.org> (raw)
In-Reply-To: <20230526091646.17318-1-johan+linaro@kernel.org>
Add the missing module device table alias to that the driver can be
autoloaded when built as a module.
Fixes: 6b149f3310a4 ("mfd: pm8008: Add driver for QCOM PM8008 PMIC")
Cc: stable@vger.kernel.org # 5.14
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
---
drivers/mfd/qcom-pm8008.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/qcom-pm8008.c b/drivers/mfd/qcom-pm8008.c
index 837246aab4ac..29ec3901564b 100644
--- a/drivers/mfd/qcom-pm8008.c
+++ b/drivers/mfd/qcom-pm8008.c
@@ -199,6 +199,7 @@ static const struct of_device_id pm8008_match[] = {
{ .compatible = "qcom,pm8008", },
{ },
};
+MODULE_DEVICE_TABLE(of, pm8008_match);
static struct i2c_driver pm8008_mfd_driver = {
.driver = {
--
2.39.3
next prev parent reply other threads:[~2023-05-26 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 9:16 [PATCH 0/2] mfd: pm8008: fix module autoloading Johan Hovold
2023-05-26 9:16 ` Johan Hovold [this message]
2023-05-26 9:22 ` [PATCH 1/2] " Konrad Dybcio
2023-05-26 9:25 ` Johan Hovold
2023-05-26 9:27 ` Konrad Dybcio
2023-06-08 15:45 ` Lee Jones
2023-06-09 6:21 ` Johan Hovold
2023-06-09 6:38 ` Lee Jones
2023-06-09 6:41 ` Johan Hovold
2023-05-26 9:16 ` [PATCH 2/2] mfd: pm8008: drop bogus i2c module alias Johan Hovold
2023-06-08 15:45 ` Lee Jones
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=20230526091646.17318-2-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).