Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	Jonas Gorski <jonas.gorski@gmail.com>
Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [BUG v6.2.7] Hitting BUG_ON() on rtw89 wireless driver startup
Date: Thu, 23 Mar 2023 08:36:37 +0000	[thread overview]
Message-ID: <6d6c51a6e29448eeb5985a59d1875c3a@realtek.com> (raw)
In-Reply-To: <4c841575-1e02-32f2-b63d-52bc0c063c82@lwfinger.net>



> -----Original Message-----
> From: Larry Finger <larry.finger@gmail.com> On Behalf Of Larry Finger
> Sent: Thursday, March 23, 2023 9:41 AM
> To: Ping-Ke Shih <pkshih@realtek.com>; Jonas Gorski <jonas.gorski@gmail.com>
> Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>; netdev@vger.kernel.org; linux-wireless@vger.kernel.org
> Subject: Re: [BUG v6.2.7] Hitting BUG_ON() on rtw89 wireless driver startup
> 
> Ping-Ke,
> 
> The patch works fine here, but I did not have the problem.
> 
> When you submit it, add a Tested-by: Larry Finger<Larry.Finger@lwfinger.net> and
> a Reviewed-by for the same address.
> 

Hi Larry,

Thanks for your test. I have submitted patch [1] with your Tested-by and Reviewed-by.
But, the patch includes additional error handling addressed during internal
review, so there is a little different from the patch I posted here. If you
don't agree current version, please NACK the patch [1]. 

Thank you.

[1] https://lore.kernel.org/linux-wireless/20230323082839.20474-1-pkshih@realtek.com/T/#u

Ping-Ke


      reply	other threads:[~2023-03-23  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 15:54 [BUG v6.2.7] Hitting BUG_ON() on rtw89 wireless driver startup Hyeonggon Yoo
2023-03-22 16:57 ` Larry Finger
2023-03-22 20:52   ` Jonas Gorski
2023-03-23  0:59     ` Ping-Ke Shih
2023-03-23  1:36       ` Larry Finger
2023-03-23  1:41       ` Larry Finger
2023-03-23  8:36         ` Ping-Ke Shih [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=6d6c51a6e29448eeb5985a59d1875c3a@realtek.com \
    --to=pkshih@realtek.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox