On 1/28/19 8:15 PM, Tony Chuang wrote:
Tony,
I had not tested rtw88 for some time, so I built a kernel with the V3 patches and
found that rtw88 crashed with a NULL pointer dereference. I did some
debugging and found that the problem was in routine rtw_chip_efuse_enable()
where fw->firmware was NULL.
Hi Larry,
This NULL pointer was found months ago and has been fixed already.
Thanks for your test :).
I am holding the patch to fix it for the next patchsets.
BTW, since rtw88 has not been accepted, could I send next patch set based on
this patch set as long as I explicitly mark that the next patch is based on the previous one?
Thanks!
You need to have that patch in whatever version is merged into the wireless
tree. It would not look very good for the initial version to crash every users
computer.
Yes, I would merge EVERY patch that you have pending into the source and submit V4.
Larry
