pinctrl: qcom: Add "and" to PIN_CONFIG_INPUT_ENABLE comment

dianders · Linus Walleij · commit b391efeeaf0b · 2023-04-11T00:22:32.000+02:00
The comment recently added talking about PIN_CONFIG_INPUT_ENABLE is clearly missing the word "and". Comments live forever, so let's fix it. Fixes: e49eabe ("pinctrl: qcom: Support OUTPUT_ENABLE; deprecate INPUT_ENABLE") Reported-by: Stephen Boyd <swboyd@chromium.org> Link: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4409769/comment/9a1d5def_e1e71db7/ Signed-off-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Link: https://lore.kernel.org/r/20230407142859.1.Ia5d70e320b60d6707c6182879097708e49b8b519@changeid Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c
@@ -517,7 +517,7 @@ static int msm_config_group_set(struct pinctrl_dev *pctldev,
 			 * The points above, explain why this _should_ be a
 			 * no-op. However, for historical reasons and to
 			 * support old device trees, we'll violate the docs
-			 * still affect the output.
+			 * and still affect the output.
 			 *
 			 * It should further be noted that this old historical
 			 * behavior actually overrides arg to 0. That means

Original file line number	Diff line number	Diff line change
`@@ -517,7 +517,7 @@ static int msm_config_group_set(struct pinctrl_dev *pctldev,`
`517`	`517`	`* The points above, explain why this _should_ be a`
`518`	`518`	`* no-op. However, for historical reasons and to`
`519`	`519`	`* support old device trees, we'll violate the docs`
`520`		`- * still affect the output.`
	`520`	`+ * and still affect the output.`
`521`	`521`	`*`
`522`	`522`	`* It should further be noted that this old historical`
`523`	`523`	`* behavior actually overrides arg to 0. That means`