mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Fri, 28 Oct 2022 17:29:44 -0700	[thread overview]
Message-ID: <Y1xz+ETEgDg5dd9u@aschofie-mobl2> (raw)
In-Reply-To: <cover.1666995639.git.tanjubrunostar0@gmail.com>

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
> 
> 

  parent reply	other threads:[~2022-10-29  0:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 23:23 Tanjuate Brunostar
2022-10-28 23:23 ` [PATCH v9 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-28 23:23 ` [PATCH v9 2/6] staging: vt6655: split long code lines in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-29  7:48   ` Greg KH
2022-10-29 19:20     ` Tanju Brunostar
2022-10-28 23:23 ` [PATCH v9 3/6] staging: vt6655: split long lines of code in s_uFillDataHead Tanjuate Brunostar
2022-10-28 23:23 ` [PATCH v9 4/6] staging: vt6655: split long lines of code in s_vGenerateTxParamete Tanjuate Brunostar
2022-10-28 23:23 ` [PATCH v9 5/6] staging: vt6655: split long lines of code in file Tanjuate Brunostar
2022-10-28 23:23 ` [PATCH v9 6/6] staging: vt6655: fix lines of code ending in a '(' Tanjuate Brunostar
2022-10-29  0:29 ` Alison Schofield [this message]
2022-10-29  7:39 ` [PATCH v9 0/6] Checkpatch cleanup in rxtx.c Greg KH

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=Y1xz+ETEgDg5dd9u@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=tanjubrunostar0@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

all inboxes | Powered by JetHome®