From: Greg KH <gregkh@linuxfoundation.org>
To: Dorine Tipo <dorine.a.tipo@gmail.com>
Cc: forest@alittletooquiet.net, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: Match parenthesis alignment
Date: Sun, 3 Mar 2024 20:30:07 +0100 [thread overview]
Message-ID: <2024030317-multitude-pelvis-bcb2@gregkh> (raw)
In-Reply-To: <20240303065640.11651-1-dorine.a.tipo@gmail.com>
On Sun, Mar 03, 2024 at 06:56:40AM +0000, Dorine Tipo wrote:
> Align parameters in static void calculate_ofdmr_parameter()
>
> This patch aligns the parameters with the opening parenthesis for better
> readability and adherence to coding style guidelines.
>
> Signed-off-by: Dorine Tipo <dorine.a.tipo@gmail.com>
> ---
> drivers/staging/vt6655/card.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Hi,
You sent 5 patches with all the same subject line, yet they did
different things :(
Please resend these, all together as a proper patch series, with unique
subjects so we can review them easier.
thanks,
greg k-h
next prev parent reply other threads:[~2024-03-03 19:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 6:56 [PATCH] staging: vt6655: Match parenthesis alignment Dorine Tipo
2024-03-03 19:30 ` Greg KH [this message]
2024-03-04 12:40 ` [PATCH v2 0/5] staging: Fix parameters alignment Dorine Tipo
2024-03-04 12:40 ` [PATCH v2 1/5] Staging: octeon: Match parenthesis alignment Dorine Tipo
2024-03-04 12:40 ` [PATCH v2 2/5] staging: vt6655: Correct parameters alignment Dorine Tipo
2024-03-04 12:40 ` [PATCH v2 3/5] staging: vt6655: Align parameters with parenthesis Dorine Tipo
2024-03-04 12:40 ` [PATCH v2 4/5] staging: vt6655: Match open parenthesis alignment Dorine Tipo
2024-03-04 12:40 ` [PATCH v2 5/5] staging: vt6655: Fix " Dorine Tipo
2024-03-04 13:55 ` [PATCH v2 0/5] staging: Fix parameters alignment Dan Carpenter
2024-03-04 14:26 ` [PATCH v3 0/1] Staging: vt6655: Parameter Alignment Improvements Dorine Tipo
2024-03-04 14:26 ` [PATCH v3 1/1] staging: vt6655: Correct parameters alignment Dorine Tipo
2024-03-04 20:53 ` Philipp Hortmann
2024-03-05 4:53 ` [PATCH v4] staging: vt6655: Match open parentheses Dorine Tipo
2024-03-05 8:10 ` [PATCH v3 1/1] staging: vt6655: Correct parameters alignment Dan Carpenter
2024-03-05 9:14 ` [PATCH v5] staging: vt6655: Match open parentheses Dorine Tipo
2024-03-05 9:32 ` [PATCH v6] " Dorine Tipo
2024-03-05 22:01 ` Philipp Hortmann
2024-03-06 4:59 ` Dan Carpenter
2024-03-06 5:40 ` Philipp Hortmann
2024-03-04 14:49 ` [PATCH V3] Staging: octeon: match parentheses alignment Dorine Tipo
2024-03-04 17:50 ` Greg KH
2024-03-05 5:14 ` [PATCH v4] Staging: octeon: Match parenthesis alignment Dorine Tipo
2024-03-05 9:23 ` [PATCH v5] " Dorine Tipo
2024-03-05 9:41 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2024-03-03 7:10 [PATCH] staging: vt6655: " Dorine Tipo
2024-03-03 7:40 [PATCH] staging: vt6655: Match parentesis alignment Dorine Tipo
2024-03-03 7:46 ` [PATCH] staging: vt6655: Match parenthesis alignment Dorine Tipo
2024-03-03 7:59 Dorine Tipo
2024-03-03 19:40 ` Philipp Hortmann
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=2024030317-multitude-pelvis-bcb2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dorine.a.tipo@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).