linux-kernel - Re: [PATCH 1/3] pinctrl: Add driver for Sunplus SP7021

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 28 Oct 2021 21:38:06 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Wells Lu 呂芳騰 <wells.lu@...plus.com>,
        Wells Lu <wellslutw@...il.com>,
        "linus.walleij@...aro.org" <linus.walleij@...aro.org>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Cc:     "qinjian@...lus1.com" <qinjian@...lus1.com>,
        "dvorkin@...bo.com" <dvorkin@...bo.com>
Subject: Re: [PATCH 1/3] pinctrl: Add driver for Sunplus SP7021

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@...aro.org \
>    --to linux-gpio@...r.kernel.org \
>    --to linux-kernel@...r.kernel.org \
>    --to robh+dt@...nel.org \
>    --to devicetree@...r.kernel.org \
>    --cc dvorkin@...bo.com \
>    --cc qinjian@...lus1.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