From: chainofflowers <chainofflowers@neuromante.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
chainofflowers <chainofflowers@posteo.net>,
ian.lin@infineon.com
Cc: Double.Lo@infineon.com, brcm80211-dev-list@broadcom.com,
brcm80211-dev-list@cypress.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com, kvalo@kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/3] brcmfmac: return error when getting invalid max_flowrings from dongle
Date: Mon, 9 Jan 2023 18:23:52 +0100 [thread overview]
Message-ID: <dd675714-c148-2810-3a19-1fc8104a5774@neuromante.net> (raw)
In-Reply-To: <3c470a48-e971-9991-e096-3adfe1cc4468@broadcom.com>
On 09.01.23 09:52, Arend van Spriel wrote:
> 6.2 is not formally released so I suppose you are an early adopter and
> aware of the risk that implies ;-) There is no real debugging needed. I
> will figure out what a sensible value would be and come up with a patch.
I am on 6.1. Version 6.1.1 works, 6.1.3 does not.
Will this patch be provided with 6.1.4? Or shall I wait until 6.2.0?
> If you can test that that would be great. Will let you know.
Sure! :)
next prev parent reply other threads:[~2023-01-09 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 3:09 [PATCH 0/3] brcmfmac: PCIE debug mechanism series Ian Lin
2022-09-29 3:09 ` [PATCH 1/3] brcmfmac: add a timer to read console periodically in PCIE bus Ian Lin
2022-10-04 7:07 ` Kalle Valo
2022-10-04 8:28 ` Kalle Valo
2022-10-10 9:53 ` Arend Van Spriel
2022-09-29 3:10 ` [PATCH 2/3] brcmfmac: return error when getting invalid max_flowrings from dongle Ian Lin
2022-10-10 9:58 ` Arend Van Spriel
2023-01-08 20:53 ` chainofflowers
2023-01-09 8:52 ` Arend van Spriel
2023-01-09 17:23 ` chainofflowers [this message]
2022-09-29 3:10 ` [PATCH 3/3] brcmfmac: dump dongle memory when attaching failed Ian Lin
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=dd675714-c148-2810-3a19-1fc8104a5774@neuromante.net \
--to=chainofflowers@neuromante.net \
--cc=Double.Lo@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chainofflowers@posteo.net \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian.lin@infineon.com \
--cc=kvalo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.