From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel@gpiccoli.net" <kernel@gpiccoli.net>,
"kernel-dev@igalia.com" <kernel-dev@igalia.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com"
<syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com>
Subject: Re: [PATCH] wifi: rtlwifi: Drastically reduce the attempts to read efuse bytes in case of failures
Date: Wed, 30 Oct 2024 15:17:34 +0200 [thread overview]
Message-ID: <c47081db-4a7a-46df-bb4b-82f8dda94460@gmail.com> (raw)
In-Reply-To: <984038be-6cc2-3acc-8ab0-5720a79dbf07@igalia.com>
On 29/10/2024 19:58, Guilherme G. Piccoli wrote:
> On 29/10/2024 13:55, Bitterblue Smith wrote:
>> [...]
>>
>> I tested your patch. Both my devices can still read the efuse.
>>
>
> This is super great, thank you! Would you like to have a Tested-by on
> that? If so, just send the name / email of your preference and I can add
> it to the V2. I'll implement the PCI guard and re-submit, thanks again!
>
> Cheers,
>
>
> Guilherme
Sure,
Tested-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
next prev parent reply other threads:[~2024-10-30 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 15:02 [PATCH] wifi: rtlwifi: Drastically reduce the attempts to read efuse bytes in case of failures Guilherme G. Piccoli
2024-10-28 1:44 ` Ping-Ke Shih
2024-10-28 14:39 ` Guilherme G. Piccoli
2024-10-29 0:50 ` Ping-Ke Shih
2024-10-29 13:20 ` Bitterblue Smith
2024-10-29 13:31 ` Guilherme G. Piccoli
2024-10-29 16:55 ` Bitterblue Smith
2024-10-29 17:58 ` Guilherme G. Piccoli
2024-10-30 13:17 ` Bitterblue Smith [this message]
2024-10-30 14:16 ` Guilherme G. Piccoli
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=c47081db-4a7a-46df-bb4b-82f8dda94460@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=gpiccoli@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.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