linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Yun Lu <luyun_611@163.com>, Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jes.Sorensen@gmail.com, kvalo@kernel.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] wifi: rtl8xxxu: fix authentication timeout due to incorrect RCR value
Date: Thu, 11 May 2023 16:56:10 +0300	[thread overview]
Message-ID: <24fd8bad-c8d7-6783-7662-e4ec86605f1d@gmail.com> (raw)
In-Reply-To: <4856a7f8.1909.18808a46ab6.Coremail.luyun_611@163.com>

On 11/05/2023 05:29, Yun Lu wrote:
> Larry  and  Bitterblue:
> 
> Thank you for your reply,  are there any further questions or suggestions on this issue?
> Could this patch be merged? There seems to be no other side effects.
> 

Your patch looks okay to me. I couldn't reproduce the bug and
I don't have any brilliant ideas, so that's it.

      parent reply	other threads:[~2023-05-11 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  2:05 [PATCH] wifi: rtl8xxxu: fix authentication timeout due to incorrect RCR value Yun Lu
2023-04-27 17:01 ` Bitterblue Smith
2023-04-28  4:30   ` Yun Lu
2023-04-27 18:01 ` Larry Finger
2023-04-28  2:00 ` Larry Finger
2023-04-28  4:25   ` wo
2023-04-28  8:25     ` Kalle Valo
2023-04-28 18:30       ` Larry Finger
2023-04-29  5:16         ` Kalle Valo
     [not found]   ` <76a784b2.2cb3.187c60f0f68.Coremail.luyun_611@163.com>
2023-04-28 17:06     ` Larry Finger
2023-04-29  3:35       ` Yun Lu
2023-04-30 10:36         ` Bitterblue Smith
2023-05-04  7:39           ` Yun Lu
2023-05-11  2:29             ` Yun Lu
2023-05-11  2:45               ` Larry Finger
2023-05-11 13:56               ` Bitterblue Smith [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=24fd8bad-c8d7-6783-7662-e4ec86605f1d@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luyun_611@163.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).