From: Randy Dunlap <rdunlap@infradead.org>
To: "Wells Lu 呂芳騰" <wells.lu@sunplus.com>,
"Wells Lu" <wellslutw@gmail.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "qinjian@cqplus1.com" <qinjian@cqplus1.com>,
"dvorkin@tibbo.com" <dvorkin@tibbo.com>
Subject: Re: [PATCH 1/3] pinctrl: Add driver for Sunplus SP7021
Date: Thu, 28 Oct 2021 21:38:06 -0700 [thread overview]
Message-ID: <0d1e4efe-bdc1-6646-384e-da7e90abc36d@infradead.org> (raw)
In-Reply-To: <930472fa25b7462aa49e33d694e4d759@sphcmbx02.sunplus.com.tw>
On 10/28/21 8:40 PM, Wells Lu 呂芳騰 wrote:
> Hi Sir,
>
> Thank you for your review.
>
> I modified errors in Kconfig you pointed out.
>
> Could you please teach me what is the next step I need to do
> (This is my first submission to Linux kernel main-line)?
Hi,
I would wait another day or two to see if there are any other
comments or reviews of the patch series, then send a v2 of
the entire series.
> 1. Should I make a patch [PATHC 1/3 v2] for Kconfig and submit
> again?
> 2. Or wait for other files of the patch [PATCH 1/3] being
> reviewed and then submit patch again.
> 3. At first patch, I used 'git send-email' command to send a
> patch series. The command is:
> git send-email \
> --to linus.walleij@linaro.org \
> --to linux-gpio@vger.kernel.org \
> --to linux-kernel@vger.kernel.org \
> --to robh+dt@kernel.org \
> --to devicetree@vger.kernel.org \
> --cc dvorkin@tibbo.com \
> --cc qinjian@cqplus1.com \
> --thread 000*.patch
> Please teach me what command options of 'git send-email'
> I should use to send the version 2 patch.
I suppose that you are using git to create patches.
I don't create patches with git, so I don't know what it takes to
create and send v2 of a patch series.
If you are not using git to create patches, you can just modify
the Subject: line in each email to include the "v2" string.
In either case, but sure to describe the changes from v1 to v2.
This description goes after (below) the "---" line. I put it before
the diffstat output with a blank line separating them.
> 4. If this is not a correct way to reply your email, please teach
> me how to reply maintainers' email.
This is fine.
thanks.
--
~Randy
next prev parent reply other threads:[~2021-10-29 4:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:55 [PATCH 0/3] Add pin control driver for Sunplus SP7021 SoC Wells Lu
2021-10-27 8:55 ` [PATCH 1/3] pinctrl: Add driver for Sunplus SP7021 Wells Lu
2021-10-27 22:12 ` Randy Dunlap
2021-10-29 3:40 ` Wells Lu 呂芳騰
2021-10-29 4:38 ` Randy Dunlap [this message]
2021-10-27 8:55 ` [PATCH 2/3] dt-bindings: pinctrl: Add dt-bindings " Wells Lu
2021-10-27 8:55 ` [PATCH 3/3] devicetree: bindings: pinctrl: Add bindings doc " Wells Lu
2021-11-09 3:59 ` Linus Walleij
[not found] ` <f315d79da3e742b4a4ec0131d6035046@sphcmbx02.sunplus.com.tw>
2021-11-18 12:20 ` Dvorkin Dmitry
2021-11-01 8:11 ` [PATCH v2 0/3] This is a patch series for pinctrl driver for Sunplus SP7021 SoC Wells Lu
2021-11-01 8:11 ` [PATCH v2 1/3] pinctrl: Add driver for Sunplus SP7021 Wells Lu
2021-11-09 4:30 ` Linus Walleij
2021-11-17 8:35 ` Wells Lu 呂芳騰
2021-11-01 8:11 ` [PATCH v2 2/3] dt-bindings: pinctrl: Add dt-bindings " Wells Lu
2021-11-12 15:37 ` Rob Herring
2021-11-18 9:03 ` Wells Lu 呂芳騰
2021-11-01 8:11 ` [PATCH v2 3/3] devicetree: bindings: pinctrl: Add bindings doc " Wells Lu
2021-11-12 15:40 ` Rob Herring
2021-11-18 9:15 ` Wells Lu 呂芳騰
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=0d1e4efe-bdc1-6646-384e-da7e90abc36d@infradead.org \
--to=rdunlap@infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=dvorkin@tibbo.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qinjian@cqplus1.com \
--cc=robh+dt@kernel.org \
--cc=wells.lu@sunplus.com \
--cc=wellslutw@gmail.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).