From: Linus Walleij <linus.walleij@linaro.org>
To: ye.xingchen@zte.com.cn
Cc: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next] pinctrl: qcom: remove duplicate included header files
Date: Mon, 28 Nov 2022 21:25:53 +0100 [thread overview]
Message-ID: <CACRpkdYQvquRysUcwOWhbsi6uELHCAToUHoSo=eHLtkN6KYXvg@mail.gmail.com> (raw)
In-Reply-To: <202211221631577017318@zte.com.cn>
On Tue, Nov 22, 2022 at 9:32 AM <ye.xingchen@zte.com.cn> wrote:
> From: ye xingchen <ye.xingchen@zte.com.cn>
>
> linux/seq_file.h is included more than once.
>
> Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
Patch applied.
Yours,
Linus Walleij
prev parent reply other threads:[~2022-11-28 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 8:31 [PATCH linux-next] pinctrl: qcom: remove duplicate included header files ye.xingchen
2022-11-28 20:25 ` Linus Walleij [this message]
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='CACRpkdYQvquRysUcwOWhbsi6uELHCAToUHoSo=eHLtkN6KYXvg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ye.xingchen@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;
as well as URLs for NNTP newsgroup(s).