From: Coiby Xu <coiby.xu@gmail.com>
To: linux-i2c@vger.kernel.org
Cc: Qii Wang <qii.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Mediatek SoC support),
linux-mediatek@lists.infradead.org (moderated list:ARM/Mediatek
SoC support), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 2/5] i2c: mediatek: remove unnecessary CONFIG_PM_SLEEP
Date: Thu, 29 Oct 2020 15:46:51 +0800 [thread overview]
Message-ID: <20201029074654.227263-2-coiby.xu@gmail.com> (raw)
In-Reply-To: <20201029074654.227263-1-coiby.xu@gmail.com>
SET_SYSTEM_SLEEP_PM_OPS has already took good care of CONFIG_PM_CONFIG.
Signed-off-by: Coiby Xu <coiby.xu@gmail.com>
---
drivers/i2c/busses/i2c-mt65xx.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-mt65xx.c b/drivers/i2c/busses/i2c-mt65xx.c
index 0cbdfbe605b5..c2939f2e5dea 100644
--- a/drivers/i2c/busses/i2c-mt65xx.c
+++ b/drivers/i2c/busses/i2c-mt65xx.c
@@ -1284,7 +1284,6 @@ static int mtk_i2c_remove(struct platform_device *pdev)
return 0;
}
-#ifdef CONFIG_PM_SLEEP
static int mtk_i2c_resume(struct device *dev)
{
int ret;
@@ -1302,7 +1301,6 @@ static int mtk_i2c_resume(struct device *dev)
return 0;
}
-#endif
static const struct dev_pm_ops mtk_i2c_pm = {
SET_SYSTEM_SLEEP_PM_OPS(NULL, mtk_i2c_resume)
--
2.28.0
next prev parent reply other threads:[~2020-10-29 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 7:46 [PATCH 1/5] i2c: qup: remove unnecessary CONFIG_PM_SLEEP Coiby Xu
2020-10-29 7:46 ` Coiby Xu [this message]
2020-10-29 7:46 ` [PATCH 3/5] i2c: brcmstb: " Coiby Xu
2020-11-04 3:28 ` Florian Fainelli
2020-10-29 7:46 ` [PATCH 4/5] i2c: nomadik: " Coiby Xu
2020-11-05 14:03 ` Linus Walleij
2020-10-29 7:46 ` [PATCH 5/5] i2c: stm32: " Coiby Xu
2020-10-29 11:31 ` Fabrice Gasnier
2020-10-29 14:18 ` Coiby Xu
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=20201029074654.227263-2-coiby.xu@gmail.com \
--to=coiby.xu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=qii.wang@mediatek.com \
/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).