All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev,
	Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Subject: [PATCH v8 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c
Date: Fri, 28 Oct 2022 17:40:52 +0000	[thread overview]
Message-ID: <cover.1666978292.git.tanjubrunostar0@gmail.com> (raw)

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

 drivers/staging/vt6655/rxtx.c | 542 ++++++++++++++++++++--------------
 1 file changed, 324 insertions(+), 218 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-10-28 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 17:40 Tanjuate Brunostar [this message]
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

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=cover.1666978292.git.tanjubrunostar0@gmail.com \
    --to=tanjubrunostar0@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.