Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 28 Oct 2022 17:29:44 -0700
From:   Alison Schofield <alison.schofield@intel.com>
To:     Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc:     gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
        linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH v9 0/6] Checkpatch cleanup in rxtx.c
Message-ID: <Y1xz+ETEgDg5dd9u@aschofie-mobl2>
References: <cover.1666995639.git.tanjubrunostar0@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cover.1666995639.git.tanjubrunostar0@gmail.com>
Precedence: bulk

Tanjuate,

Wow - I've seen 4 revs of this in 12 hours?!

I reviewed each Patch against the feedback previously
offered, and it was not addressed, so I'm going to NAK
this set and ask you to rework carefully before resending.
I expect to see each specific piece of reviewer feedback,
called out as addressed in the changelog.

BTW - I still prefer a single patch at a time while you are
learning these mechanics, and to make sure that this type
of patch is going to be accepted.

If you are still amenable to doing that, keep the version,
but only send one patch at a time. When one gets accepted,
apply those learnings to the second patch, and so on.

That should go more smoothly for you and your reviewers.

Alison

On Fri, Oct 28, 2022 at 11:23:21PM +0000, Tanjuate Brunostar wrote:
> v9: reorganized the changelog messages on this patch
> 
> v8: made commit messages clearer, unsuccessfuly
> 
> v7: made log messages less confusing
> 
> v6: fixed some errors on commit messages
> 
> v5: shortend changelog comments
> 
> v4: made some changes on the code
> 
> v3: fixed compilation errors
> 
> v2: tried fixing compilation erros unsuccessfuly
> 
> Tanjuate Brunostar (6):
>   staging: vt6655: fix lines of code ending in a '('
>   staging: vt6655: split long lines of code in s_uGetRTSCTSDuration
>   staging: vt6655: split long lines of code in s_uFillDataHead
>   staging: vt6655: split long lines of code in s_vGenerateTxParamete
>   staging: vt6655: split long lines of code in some functions
>   staging: vt6655: fix lines of code ending in a '('
> 
>  drivers/staging/vt6655/rxtx.c | 542 ++++++++++++++++++++--------------
>  1 file changed, 324 insertions(+), 218 deletions(-)
> 
> -- 
> 2.34.1
> 
>