From: Dan Carpenter <dan.carpenter@linaro.org>
To: Luka Gejak <lukagejak5@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/5] staging: rtl8723bs: fix OOB read and perform
Date: Sat, 31 Jan 2026 16:57:06 +0300 [thread overview]
Message-ID: <aX4KMi5SKkFwBPtR@stanley.mountain> (raw)
In-Reply-To: <aX3-9zMnUBVUKP1L@stanley.mountain>
On Sat, Jan 31, 2026 at 04:09:11PM +0300, Dan Carpenter wrote:
> On Fri, Jan 30, 2026 at 07:16:15PM +0100, Luka Gejak wrote:
> > Changes in v5:
> > - Corrected commit message line wrapping to 72 characters.
> > - Removed blank lines between tags in the Signed-off-by block.
> > - Removed "Security:" prefix from subject lines.
>
> Looks okay.
>
> Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
>
Or we could apply v6 with the tweaked subjects.
regards,
dan carpenter
next prev parent reply other threads:[~2026-01-31 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 18:16 [PATCH v5 0/5] staging: rtl8723bs: fix OOB read and perform Luka Gejak
2026-01-30 18:16 ` [PATCH v5 1/5] staging: rtl8723bs: fix potential out-of-bounds Luka Gejak
2026-01-30 18:16 ` [PATCH v5 2/5] staging: rtl8723bs: rename u1bTmp to val Luka Gejak
2026-01-30 18:16 ` [PATCH v5 3/5] staging: rtl8723bs: fix spacing around operators Luka Gejak
2026-01-30 18:16 ` [PATCH v5 4/5] staging: rtl8723bs: modernize hex output in Luka Gejak
2026-01-30 18:16 ` [PATCH v5 5/5] staging: rtl8723bs: remove dead debugging code Luka Gejak
2026-01-30 18:47 ` [PATCH v5 0/5] staging: rtl8723bs: fix OOB read and perform Luka Gejak
2026-01-31 13:09 ` Dan Carpenter
2026-01-31 13:57 ` Dan Carpenter [this message]
2026-01-31 14:05 ` Luka Gejak
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=aX4KMi5SKkFwBPtR@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lukagejak5@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