Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nayana Mariyappa <nayana.mariyappa@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v4 0/4] staging: rtl8723bs: coding style fixes
Date: Mon, 12 Jan 2026 11:56:33 +0100	[thread overview]
Message-ID: <2026011253-opulently-shredder-f586@gregkh> (raw)
In-Reply-To: <20260112104654.45175-1-nayana.mariyappa@gmail.com>

On Mon, Jan 12, 2026 at 10:46:50AM +0000, Nayana Mariyappa wrote:
> This is a series of 4 small coding style fixes for rtl8723bs. Each patch is
> self-contained and focuses on a single logical change, as requested.
> 
> Changes since v1:
> - Split the original patch into 4 separate patches.
> - Each patch now fixes one coding style issue.
> - The previous patch fixing the non-kernel-doc comment has been merged
>   into this v4 series; the separate patch is now retired.

But this is v4, what happened between 1-2, and 2-3, and then 3-4?

Also, please slow down, take some time, relax, and redo a v5 tomorrow.
There's no rush here.  Take the time to get this right.

thanks,

greg k-h

  parent reply	other threads:[~2026-01-12 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 10:46 [PATCH v4 0/4] staging: rtl8723bs: coding style fixes Nayana Mariyappa
2026-01-12 10:46 ` [PATCH v4 1/4] staging: rtl8723bs: fix block comment style Nayana Mariyappa
2026-01-12 10:57   ` Greg KH
2026-01-12 10:46 ` [PATCH v4 2/4] staging: rtl8723bs: remove extra blank lines Nayana Mariyappa
2026-01-12 10:46 ` [PATCH v4 3/4] staging: rtl8723bs: add blank lines after declarations Nayana Mariyappa
2026-01-12 10:46 ` [PATCH v4 4/4] staging: rtl8723bs: expand multiple assignment into separate statements Nayana Mariyappa
2026-01-12 10:56 ` Greg KH [this message]
2026-01-12 11:37 ` [PATCH v4 0/4] staging: rtl8723bs: coding style fixes Dan Carpenter

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=2026011253-opulently-shredder-f586@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=nayana.mariyappa@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