public inbox for linux-staging@lists.linux.dev
 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 v2 0/4] staging: rtl8723bs: coding style fixes
Date: Mon, 12 Jan 2026 10:33:19 +0100	[thread overview]
Message-ID: <2026011210-unstuffed-undrafted-eadf@gregkh> (raw)
In-Reply-To: <20260112043429.42615-1-nayana.mariyappa@gmail.com>

On Mon, Jan 12, 2026 at 04:34:25AM +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.
> 
> Patches in this series:
> 
> 1/4 staging: rtl8723bs: fix block comment style
> 2/4 staging: rtl8723bs: remove extra blank lines
> 3/4 staging: rtl8723bs: add blank lines after declarations
> 4/4 staging: rtl8723bs: expand multiple assignment into separate statements
> 
> Signed-off-by: Nayana Mariyappa <nayana.mariyappa@gmail.com>
> 

This should have been v3, right?

thanks,

greg k-h

  parent reply	other threads:[~2026-01-12  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  4:34 [PATCH v2 0/4] staging: rtl8723bs: coding style fixes Nayana Mariyappa
2026-01-12  4:34 ` [PATCH v2 1/4] staging: rtl8723bs: fix block comment style Nayana Mariyappa
2026-01-12  9:32   ` Greg KH
2026-01-12  4:34 ` [PATCH v2 2/4] staging: rtl8723bs: remove extra blank lines Nayana Mariyappa
2026-01-12  4:34 ` [PATCH v2 3/4] staging: rtl8723bs: add blank lines after declarations Nayana Mariyappa
2026-01-12  4:34 ` [PATCH v2 4/4] staging: rtl8723bs: expand multiple assignment into separate statements Nayana Mariyappa
2026-01-12  9:33 ` Greg KH [this message]
2026-01-12 10:48   ` [PATCH v2 0/4] staging: rtl8723bs: coding style fixes Nayana Mariyappa
  -- strict thread matches above, loose matches on Subject: below --
2026-01-09 11:04 Nayana Mariyappa
2026-01-11 13:02 ` Greg Kroah-Hartman
     [not found]   ` <CAN1kxfyz5K9kUVY3yFCKYdaQHuED-oNCBWCcLL+bT7YQ_VVXRQ@mail.gmail.com>
     [not found]     ` <2026011236-drank-monopoly-916a@gregkh>
     [not found]       ` <CAN1kxfyv7MBC4yWs1X6cO549pu2MisPqudyC0Cx7NzJFmrDUXA@mail.gmail.com>
2026-01-12  9:33         ` Greg Kroah-Hartman

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=2026011210-unstuffed-undrafted-eadf@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