All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev
Subject: Re: [PATCH v3 0/6] a series of checkpatch fixes on the file: rxtx.c
Date: Sat, 22 Oct 2022 09:35:37 +0200	[thread overview]
Message-ID: <Y1OdSYH45MNbp03k@kroah.com> (raw)
In-Reply-To: <20221022070612.13009-1-tanjubrunostar0@gmail.com>

On Sat, Oct 22, 2022 at 07:06:06AM +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
> 
> 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_vGenerateTxParameter
>   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 | 532 ++++++++++++++++++++--------------
>  1 file changed, 321 insertions(+), 211 deletions(-)
> 
> -- 
> 2.34.1
> 
> 

Any reason you do not have "staging: vt6655:" as the prefix for this 0/X
email subject line?

thanks,

greg k-h

  parent reply	other threads:[~2022-10-22  8:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  7:06 [PATCH v3 0/6] a series of checkpatch fixes on the file: rxtx.c Tanjuate Brunostar
2022-10-22  7:06 ` [PATCH v3 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-22  7:18   ` Joe Perches
2022-10-22  7:35     ` Tanju Brunostar
2022-10-22  8:10   ` Greg KH
2022-10-22  8:24     ` Tanju Brunostar
2022-10-22  7:06 ` [PATCH v3 2/6] staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-22  8:11   ` Greg KH
2022-10-22  8:26     ` Tanju Brunostar
2022-10-22  7:06 ` [PATCH v3 3/6] staging: vt6655: refactor long lines of code in s_uFillDataHead Tanjuate Brunostar
2022-10-22  8:12   ` Greg KH
2022-10-22  8:27     ` Tanju Brunostar
2022-10-22  7:06 ` [PATCH v3 4/6] staging: vt6655: refactor long lines of code in s_vGenerateTxParameter Tanjuate Brunostar
2022-10-22  8:14   ` Greg KH
2022-10-22  8:28     ` Tanju Brunostar
2022-10-22  7:06 ` [PATCH v3 5/6] staging: vt6655: refactor long lines of code in the rest of the file Tanjuate Brunostar
2022-10-22  8:14   ` Greg KH
2022-10-22  8:29     ` Tanju Brunostar
2022-10-22  7:06 ` [PATCH v3 6/6] staging: vt6655: refactor code to avoid a line ending in '(' Tanjuate Brunostar
2022-10-22  7:35 ` Greg KH [this message]
2022-10-22  8:22   ` [PATCH v3 0/6] a series of checkpatch fixes on the file: rxtx.c Tanju Brunostar

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=Y1OdSYH45MNbp03k@kroah.com \
    --to=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 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.