All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Zong-Zhe Yang <kevin_yang@realtek.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Cc: Kalle Valo <kvalo@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: RE: [PATCH next] wifi: rtw89: unlock on error path in rtw89_ops_unassign_vif_chanctx()
Date: Tue, 22 Oct 2024 03:32:23 +0000	[thread overview]
Message-ID: <931c79c15bc04be99bb87a9826cf2b04@realtek.com> (raw)
In-Reply-To: <6a80d4adc51f4ea884b5e02f16d8aaed@realtek.com>

Zong-Zhe Yang <kevin_yang@realtek.com> wrote:
> Dan Carpenter <dan.carpenter@linaro.org> wrote:
> >
> > [...]
> >
> > @@ -1373,6 +1373,7 @@ static void rtw89_ops_unassign_vif_chanctx(struct ieee80211_hw
> > *hw,
> >
> >         rtwvif_link = rtwvif->links[link_conf->link_id];
> >         if (unlikely(!rtwvif_link)) {
> > +               mutex_unlock(&rtwdev->mutex);
> >                 rtw89_err(rtwdev,
> >                           "%s: rtwvif link (link_id %u) is not active\n",
> >                           __func__, link_conf->link_id);
> >
> 
> Acked-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> 

Thanks for the ack. 

Acked-by is often used by the maintainer, so I will change it to Reviewed-by
during committing. 



  reply	other threads:[~2024-10-22  3:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  9:14 [PATCH next] wifi: rtw89: unlock on error path in rtw89_ops_unassign_vif_chanctx() Dan Carpenter
2024-10-22  3:27 ` Zong-Zhe Yang
2024-10-22  3:32   ` Ping-Ke Shih [this message]
2024-10-23  8:35     ` Dan Carpenter
2024-10-23  9:38       ` Kalle Valo
2024-10-23 10:06         ` Dan Carpenter
2024-10-25  2:28 ` Ping-Ke Shih

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=931c79c15bc04be99bb87a9826cf2b04@realtek.com \
    --to=pkshih@realtek.com \
    --cc=dan.carpenter@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kevin_yang@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.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.