From: "Salman Alghamdi" <me@cipherat.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: luka.gejak@linux.dev, straube.linux@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v6 1/8] staging: rtl8723bs: fix buffer over-read in rtw_update_protection
Date: Fri, 08 May 2026 00:56:09 +0300 [thread overview]
Message-ID: <eb3759ee-ecfb-f707-4105-6029d236ce3a@cipherat.com> (raw)
In-Reply-To: <2026050434-construct-starter-5468@gregkh>
On May 04, 2026 12:35 +03, Greg KH <gregkh@linuxfoundation.org> wrote:
> > drivers/staging/rtl8723bs/core/rtw_mlme.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
>
> You should not mix patches for the current release (i.e. this one), with
> patches for the next release (i.e. the rest of the patches in this
> series), as that means I can't take the full series for either :(
>
> Please break this up into two different sets of patches and resend them
> that way.
Hi Greg,
Thank you for the review.
Two questions before I resend:
1. How do I tell which release a patch targets? Is it purely based on whether it's a bug fix (current release) vs. a new change (next release), or is there a more specific rule I should follow?
2. For versioning the split series, should the bug fix patch restart at v1, and the rest of the series continue at v7? Or should I keep them sequential (bug fix as v7, next-release patches as v8)?
Thanks,
Salman Alghamdi
next parent reply other threads:[~2026-05-07 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260428164513.763471-1-me@cipherat.com>
[not found] ` <20260428164513.763471-2-me@cipherat.com>
[not found] ` <2026050434-construct-starter-5468@gregkh>
2026-05-07 21:56 ` Salman Alghamdi [this message]
2026-05-08 5:00 ` [PATCH v6 1/8] staging: rtl8723bs: fix buffer over-read in rtw_update_protection Greg KH
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=eb3759ee-ecfb-f707-4105-6029d236ce3a@cipherat.com \
--to=me@cipherat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@linux.dev \
--cc=stable@vger.kernel.org \
--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