mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Can Peng <pengcan@kylinos.cn>
To: arend.vanspriel@broadcom.com
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
	brcm80211-dev-list.pdl@broadcom.com,
	linux-kernel@vger.kernel.org, Can Peng <pengcan@kylinos.cn>
Subject: [PATCH v2 0/2] wifi: brcmfmac: validate msgbuf flowring IDs
Date: Mon,  3 Aug 2026 15:12:57 +0800	[thread overview]
Message-ID: <20260803071259.546631-1-pengcan@kylinos.cn> (raw)

Clean up the excess blank lines in msgbuf.c first, then validate
firmware supplied msgbuf flowring IDs before converting them to internal
flow IDs and using them as bit and array indexes.

Changes in v2:
- Add a preparatory cleanup to use a single blank line between functions
  and declarations in msgbuf.c.
- Rebase the flowring ID validation change on top of the cleanup.
- Link to v1:
  https://lore.kernel.org/all/20260723055618.550834-1-pengcan@kylinos.cn/

Can Peng (2):
  wifi: brcmfmac: remove extra blank lines in msgbuf.c
  wifi: brcmfmac: validate msgbuf flowring IDs before use

 .../broadcom/brcm80211/brcmfmac/msgbuf.c      | 84 +++++++++----------
 1 file changed, 39 insertions(+), 45 deletions(-)

-- 
2.53.0

             reply	other threads:[~2026-08-03  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  7:12 Can Peng [this message]
2026-08-03  7:12 ` [PATCH v2 1/2] wifi: brcmfmac: remove extra blank lines in msgbuf.c Can Peng
2026-08-03  7:12 ` [PATCH v2 2/2] wifi: brcmfmac: validate msgbuf flowring IDs before use Can Peng
2026-08-03  7:20 ` [PATCH v2 0/2] wifi: brcmfmac: validate msgbuf flowring IDs Johannes Berg

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=20260803071259.546631-1-pengcan@kylinos.cn \
    --to=pengcan@kylinos.cn \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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®