mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Can Peng <pengcan@kylinos.cn>, 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
Subject: Re: [PATCH v2 0/2] wifi: brcmfmac: validate msgbuf flowring IDs
Date: Mon, 03 Aug 2026 09:20:56 +0200	[thread overview]
Message-ID: <5811c9927b0fd5dd2287101a2c98a4eac3b6c5ca.camel@sipsolutions.net> (raw)
In-Reply-To: <20260803071259.546631-1-pengcan@kylinos.cn>

On Mon, 2026-08-03 at 15:12 +0800, Can Peng wrote:
> 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.

Too late, I applied the other changes yesterday, and while I can rebase,
I'm not going to do that now for just some whitespace. Feel free to send
a cleanup on top of current wireless-next.

johannes

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  7:12 Can Peng
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 ` Johannes Berg [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=5811c9927b0fd5dd2287101a2c98a4eac3b6c5ca.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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 \
    --cc=pengcan@kylinos.cn \
    /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®