mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Salman Alghamdi <me@cipherat.com>
Cc: straube.linux@gmail.com, error27@gmail.com, luka.gejak@linux.dev,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/6] staging: rtl8723bs: rtw_mlme: line length cleanup
Date: Thu, 21 May 2026 12:38:33 +0200	[thread overview]
Message-ID: <2026052112-shortwave-imperial-c31b@gregkh> (raw)
In-Reply-To: <20260513203611.31872-1-me@cipherat.com>

On Wed, May 13, 2026 at 11:34:58PM +0300, Salman Alghamdi wrote:
> This series cleans up lines exceeding 100 columns in rtw_mlme.c,
> along with minor readability improvements.
> 
> The two bug fix patches previously included in this series have been
> split out and sent separately as standalone patches at Greg's request.
> 
> Changes since v7:
> - Split bounds check fix into a separate standalone patch per Greg KH's
>   review

Not all of these applied to my tree, can you rebase against the latest
staging-next branch and resend the remaining ones?

thanks,

greg k-h

      parent reply	other threads:[~2026-05-21 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 20:34 Salman Alghamdi
2026-05-13 20:34 ` [PATCH v8 1/6] staging: rtl8723bs: rtw_mlme: wrap lines exceeding 100 columns Salman Alghamdi
2026-05-13 20:35 ` [PATCH v8 2/6] staging: rtl8723bs: rtw_mlme: wrap rtw_sitesurvey_cmd condition Salman Alghamdi
2026-05-13 20:35 ` [PATCH v8 3/6] staging: rtl8723bs: rtw_mlme: extract local variables for long expressions Salman Alghamdi
2026-05-13 20:35 ` [PATCH v8 4/6] staging: rtl8723bs: rtw_mlme: remove dead commented-out code Salman Alghamdi
2026-05-13 20:35 ` [PATCH v8 5/6] staging: rtl8723bs: rtw_mlme: consolidate capability comparisons lines Salman Alghamdi
2026-05-13 20:35 ` [PATCH v8 6/6] staging: rtl8723bs: rtw_mlme: add blank line for readability Salman Alghamdi
2026-05-21 10:38 ` Greg KH [this message]

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=2026052112-shortwave-imperial-c31b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=error27@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=luka.gejak@linux.dev \
    --cc=me@cipherat.com \
    --cc=straube.linux@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
all inboxes | Powered by JetHome®