From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Wang Jinchao <wangjinchao@xfusion.com>,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: stone.xulei@xfusion.com
Subject: Re: [PATCH] pinctrl: qcom: lpass-lpi: remove duplicated include
Date: Sat, 16 Dec 2023 01:04:04 +0100 [thread overview]
Message-ID: <f355630b-4010-4785-a9c9-5f65ef016db0@linaro.org> (raw)
In-Reply-To: <202312151810+0800-wangjinchao@xfusion.com>
On 15.12.2023 11:11, Wang Jinchao wrote:
> remove the second #include <linux/seq_file.h>
>
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
Lol, nice find
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
next prev parent reply other threads:[~2023-12-16 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 10:11 [PATCH] pinctrl: qcom: lpass-lpi: remove duplicated include Wang Jinchao
2023-12-16 0:04 ` Konrad Dybcio [this message]
2023-12-20 11:30 ` Linus Walleij
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=f355630b-4010-4785-a9c9-5f65ef016db0@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stone.xulei@xfusion.com \
--cc=wangjinchao@xfusion.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).