public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.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 v8 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c
Date: Sat, 29 Oct 2022 09:28:26 +0700	[thread overview]
Message-ID: <Y1yPyt5NsvfSL3UC@debian.me> (raw)
In-Reply-To: <cover.1666978292.git.tanjubrunostar0@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

On Fri, Oct 28, 2022 at 05:40:52PM +0000, Tanjuate Brunostar wrote:
> The fixes are similar, mostly long lines splitting. I had to make
> serveral patches to ease the work of inspectors
> 
> v2: fixed a compilation error found by the kernel test robot and
> recompiled the code
> 
> v3: tends out the error persisted in the second version. this version is
> a correction of that
> 
> v4: did some corrections as recommended by Greg KH
> 
> v5: shortend changelog comments as recommended by Greg KH
> 
> v6: did some corrections as recommended by Greg KH
> 
> v7: fixed some errors on my changelog comments
> 
> v8: fixed some errors pointed out by Philipp Hortmann
> 
> Tanjuate Brunostar (6):
>   staging: vt6655: fix lines ending in a '('
>   staging: vt6655: fix long lines of code in s_uGetRTSCTSDuration
>   staging: vt6655: fix long lines of code in s_uFillDataHead
>   staging: vt6655: fix long lines of code in s_vGenerateTxParamete
>   staging: vt6655: fix long lines of code in the rest of the file
>   staging: vt6655: fix lines of code ending in a '('
> 

You messed up your patchset...; the shortlog above says "fix longlines"
but individual patch subject says "refactor". Well, refactoring
means resturcturing and improving it without introducing new
functionality or changing behavior, which is really changing existing
code. However, your patchset only do visual formatting, right?

Also, have you ever at least compile-test your patchset (make W=1 and
enabling CONFIG_WERROR)?

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 17:40 [PATCH v8 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 2/6] staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 3/6] staging: vt6655: refactor long lines of code in s_uFillDataHead Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 4/6] staging: vt6655: refactor long lines of code in s_vGenerateTxParamete Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 5/6] staging: vt6655: refactor long lines of code in the rest of the file Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v8 6/6] staging: vt6655: fix lines of code ending in a '(' Tanjuate Brunostar
2022-10-28 18:11 ` [PATCH v8 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c Alison Schofield
2022-10-28 18:17   ` Tanju Brunostar
2022-10-29  2:28 ` Bagas Sanjaya [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=Y1yPyt5NsvfSL3UC@debian.me \
    --to=bagasdotme@gmail.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