linux-kernel - Re: [regression] ath11k broken in v6.7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 02 Feb 2024 13:34:37 +0200
From: Kalle Valo <kvalo@...nel.org>
To: "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info>
Cc: Linux regressions mailing list <regressions@...ts.linux.dev>,
  ath11k@...ts.infradead.org,  linux-wireless@...r.kernel.org,
  linux-kernel@...r.kernel.org
Subject: Re: [regression] ath11k broken in v6.7

"Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info> writes:
>> One more question, I promise it's the last one :) When using the Closes
>> tag in patches does it matter which URL is used, either the original or
>> the duplicate? For example, do these both tags close the issue:
>> 
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=325423423423542
>> Closes: https://lore.kernel.org/not_relevant/msgid-423423423423423423/
>
> Yes, you can use either or both of them together to make regzbot close a
> issue and it's duplicates. But to make Linus happy I guess he'd prefer
> to have both links in there, if those are reports from different people
> that contain background information that might sooner or later be handy
> to have at hand.

Good point, I didn't consider that. I think I have now a good grasp of
regzbot and I'll try to use it actively from now on. Good luck for the
rewrite, I hope you get it finished soon.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches