All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nayana Mariyappa <nayana.mariyappa@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] staging: rtl8723bs: coding style fixes
Date: Sun, 11 Jan 2026 14:02:11 +0100	[thread overview]
Message-ID: <2026011142-stability-coping-e3bc@gregkh> (raw)
In-Reply-To: <20260109110417.16359-1-nayana.mariyappa@gmail.com>

On Fri, Jan 09, 2026 at 11:04:16AM +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>
> 

Something went wrong with this submission, it seems to be broken up into
two "series".  Here's how it looks in my inbox:

      T Jan 09 Nayana Mariyapp (  16) [PATCH v2 0/4] staging: rtl8723bs: coding style fixes
      T Jan 09 Nayana Mariyapp (  31) └─>[PATCH v2 1/4] staging: rtl8723bs: fix block comment style
      T Jan 09 Nayana Mariyapp (  25) [PATCH v2 2/4] staging: rtl8723bs: remove extra blank lines
      T Jan 09 Nayana Mariyapp (  27) ├─>[PATCH v2 4/4] staging: rtl8723bs: expand multiple assignment into separate statements
      T Jan 09 Nayana Mariyapp (  25) └─>[PATCH v2 3/4] staging: rtl8723bs: add blank lines after declarations

And this also mirrors what shows up on lore.kernel.org:
	https://lore.kernel.org/r/20260109110417.16359-1-nayana.mariyappa@gmail.com

Can you fix up your git send-email settings to send these all out at once to
properly be linked together?

Thanks,

greg k-h


  parent reply	other threads:[~2026-01-11 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 11:04 [PATCH v2 0/4] staging: rtl8723bs: coding style fixes Nayana Mariyappa
2026-01-09 11:04 ` [PATCH v2 1/4] staging: rtl8723bs: fix block comment style Nayana Mariyappa
2026-01-11 13:02 ` Greg Kroah-Hartman [this message]
     [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         ` [PATCH v2 0/4] staging: rtl8723bs: coding style fixes Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2026-01-12  4:34 Nayana Mariyappa
2026-01-12  9:33 ` Greg KH
2026-01-12 10:48   ` Nayana Mariyappa

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=2026011142-stability-coping-e3bc@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 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.