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 v7 0/7] staging: rtl8723bs: rtw_mlme: line length cleanup
Date: Mon, 11 May 2026 10:08:42 +0200 [thread overview]
Message-ID: <2026051131-parchment-mouse-2136@gregkh> (raw)
In-Reply-To: <20260508222725.24075-1-me@cipherat.com>
On Sat, May 09, 2026 at 01:26:56AM +0300, Salman Alghamdi wrote:
> This series cleans up lines exceeding 100 columns in rtw_mlme.c,
> along with minor readability improvements.
>
> The buffer over-read fix previously included in this series has been
> split out and sent separately as a standalone patch at Greg's request.
>
> Changes since v6:
> - Split fix patch into a separate series per Greg KH's review
Always show the changes from previous versions as well.
thanks,
greg k-h
prev parent reply other threads:[~2026-05-11 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 22:26 [PATCH v7 0/7] staging: rtl8723bs: rtw_mlme: line length cleanup Salman Alghamdi
2026-05-08 22:26 ` [PATCH v7 1/7] staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction Salman Alghamdi
2026-05-11 8:08 ` Greg KH
2026-05-08 22:26 ` [PATCH v7 2/7] staging: rtl8723bs: rtw_mlme: wrap lines exceeding 100 columns Salman Alghamdi
2026-05-08 22:26 ` [PATCH v7 3/7] staging: rtl8723bs: rtw_mlme: wrap rtw_sitesurvey_cmd condition Salman Alghamdi
2026-05-08 22:27 ` [PATCH v7 4/7] staging: rtl8723bs: rtw_mlme: extract local variables for long expressions Salman Alghamdi
2026-05-08 22:27 ` [PATCH v7 5/7] staging: rtl8723bs: rtw_mlme: remove dead commented-out code Salman Alghamdi
2026-05-08 22:27 ` [PATCH v7 6/7] staging: rtl8723bs: rtw_mlme: consolidate capability comparisons lines Salman Alghamdi
2026-05-08 22:27 ` [PATCH v7 7/7] staging: rtl8723bs: rtw_mlme: add blank line for readability Salman Alghamdi
2026-05-11 8:08 ` 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=2026051131-parchment-mouse-2136@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