From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>,
gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH v4 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c
Date: Mon, 24 Oct 2022 20:09:34 +0200 [thread overview]
Message-ID: <64d0f316-3e72-877d-0f6b-3db1d67877ac@gmail.com> (raw)
In-Reply-To: <cover.1666605225.git.tanjubrunostar0@gmail.com>
On 10/24/22 12:01, 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
>
> Tanjuate Brunostar (6):
> staging: vt6655: fix lines ending in a '('
> staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration
> staging: vt6655: refactor long lines of code in s_uFillDataHead
> staging: vt6655: refactor long lines of code in s_vGenerateTxParamete
> staging: vt6655: refactor long lines of code in the rest of the file
> staging: vt6655: refactor code to avoid a line ending in '('
>
> drivers/staging/vt6655/rxtx.c | 542 ++++++++++++++++++++--------------
> 1 file changed, 324 insertions(+), 218 deletions(-)
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2022-10-24 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 10:01 Tanjuate Brunostar
2022-10-24 10:01 ` [PATCH v4 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-24 10:01 ` [PATCH v4 2/6] staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-25 17:24 ` Greg KH
2022-10-24 10:01 ` [PATCH v4 3/6] staging: vt6655: refactor long lines of code in s_uFillDataHead Tanjuate Brunostar
2022-10-24 10:01 ` [PATCH v4 4/6] staging: vt6655: refactor long lines of code in s_vGenerateTxParamete Tanjuate Brunostar
2022-10-24 10:01 ` [PATCH v4 5/6] staging: vt6655: refactor long lines of code in the rest of the file Tanjuate Brunostar
2022-10-24 10:01 ` [PATCH v4 6/6] staging: vt6655: refactor code to avoid a line ending in '(' Tanjuate Brunostar
2022-10-24 18:09 ` Philipp Hortmann [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=64d0f316-3e72-877d-0f6b-3db1d67877ac@gmail.com \
--to=philipp.g.hortmann@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
Powered by JetHome