From: Kalle Valo <kvalo@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Ping-Ke Shih <pkshih@realtek.com>,
Zong-Zhe Yang <kevin_yang@realtek.com>,
"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: Wed, 23 Oct 2024 12:38:38 +0300 [thread overview]
Message-ID: <87v7xjma5d.fsf@kernel.org> (raw)
In-Reply-To: <2e85c84b-31bf-484b-b3e2-9285999bb2e4@stanley.mountain> (Dan Carpenter's message of "Wed, 23 Oct 2024 11:35:09 +0300")
Dan Carpenter <dan.carpenter@linaro.org> writes:
> On Tue, Oct 22, 2024 at 03:32:23AM +0000, Ping-Ke Shih wrote:
>
>> 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.
>
> To me Acked by just means you're okay with the patch. When I use it, it means I
> don't feel qualified or interested enough to do a full review. For example, if
> I complain about a v1 patch and they fix my issue in v2 then I like to say that
> I'm okay with it. In that case I'll use Reviewed-by for a full review or Acked
> by if the bits that I care about are okay. I don't like to complain and then
> just go silent.
>
> In the end, it doesn't make any difference. You'll get CC'd on bug reports to
> do with the patch and you'll potentially feel bad for not spotting the bug, I
> guess.
I have understood that Acked-by should be only used by the corresponding
maintainers and the documentation seems to say the same:
https://docs.kernel.org/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
The reason I ask non-maintainers avoid using Acked-by is that it messes
our patchwork listings (it counts both Acked-by and Reviewed-by tags).
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-10-23 9:38 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
2024-10-23 8:35 ` Dan Carpenter
2024-10-23 9:38 ` Kalle Valo [this message]
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=87v7xjma5d.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kevin_yang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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