From: <zhang.songyi@zte.com.cn>
To: <andersson@kernel.org>, <agross@kernel.org>,
<konrad.dybcio@somainline.org>
Cc: <linus.walleij@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <xue.zhihong@zte.com.cn>,
<jiang.xuexin@zte.com.cn>
Subject: [PATCH linux-next] pinctrl: qcom: remove duplicate include
Date: Wed, 2 Nov 2022 10:46:20 +0800 (CST) [thread overview]
Message-ID: <202211021046202606659@zte.com.cn> (raw)
From 6b941a80348b4d8b862072ecec4df41a43368c60 Mon Sep 17 00:00:00 2001
From: zhang songyi <zhang.songyi@zte.com.cn>
Date: Wed, 2 Nov 2022 10:21:53 +0800
Subject: [PATCH linux-next] pinctrl: qcom: remove duplicate include
'linux/seq_file.h' included in
'drivers/pinctrl/qcom/pinctrl-lpass-lpi.c,
drivers/pinctrl/qcom/pinctrl-msm.c,
drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c,
drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c' is duplicated.
Reported-by: Zeal Robot <zealci@zte.com.cn>
Signed-off-by: zhang songyi <zhang.songyi@zte.com.cn>
---
drivers/pinctrl/qcom/pinctrl-lpass-lpi.c | 2 --
drivers/pinctrl/qcom/pinctrl-msm.c | 2 --
drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c | 2 --
drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c | 2 --
4 files changed, 8 deletions(-)
diff --git a/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c b/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
index d5cfa91e2eff..90648fc11647 100644
--- a/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
+++ b/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
@@ -283,8 +283,6 @@ static void lpi_gpio_set(struct gpio_chip *chip, unsigned int pin, int value)
}
#ifdef CONFIG_DEBUG_FS
-#include <linux/seq_file.h>
-
static unsigned int lpi_regval_to_drive(u32 val)
{
return (val + 1) * 2;
diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c
index 8fbb953c4bbe..0d2d3e83e929 100644
--- a/drivers/pinctrl/qcom/pinctrl-msm.c
+++ b/drivers/pinctrl/qcom/pinctrl-msm.c
@@ -622,8 +622,6 @@ static void msm_gpio_set(struct gpio_chip *chip, unsigned offset, int value)
}
#ifdef CONFIG_DEBUG_FS
-#include <linux/seq_file.h>
-
static void msm_gpio_dbg_show_one(struct seq_file *s,
struct pinctrl_dev *pctldev,
struct gpio_chip *chip,
diff --git a/drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c b/drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c
index b1748791a01e..cf69f208dfb8 100644
--- a/drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c
+++ b/drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c
@@ -536,8 +536,6 @@ static int pm8xxx_gpio_of_xlate(struct gpio_chip *chip,
#ifdef CONFIG_DEBUG_FS
-#include <linux/seq_file.h>
-
static void pm8xxx_gpio_dbg_show_one(struct seq_file *s,
struct pinctrl_dev *pctldev,
struct gpio_chip *chip,
diff --git a/drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c b/drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c
index 30a934245c1b..71bbf1f1599a 100644
--- a/drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c
+++ b/drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c
@@ -536,8 +536,6 @@ static int pm8xxx_mpp_of_xlate(struct gpio_chip *chip,
#ifdef CONFIG_DEBUG_FS
-#include <linux/seq_file.h>
-
static void pm8xxx_mpp_dbg_show_one(struct seq_file *s,
struct pinctrl_dev *pctldev,
struct gpio_chip *chip,
--
2.15.2
reply other threads:[~2022-11-02 2:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202211021046202606659@zte.com.cn \
--to=zhang.songyi@zte.com.cn \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=jiang.xuexin@zte.com.cn \
--cc=konrad.dybcio@somainline.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=xue.zhihong@zte.com.cn \
/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