Re: [regression] ath11k broken in v6.7

[Linux regression tracking (Thorsten Leemhuis)]

On 02.02.24 11:45, Kalle Valo wrote:
> Thorsten Leemhuis <regressions@xxxxxxxxxxxxx> writes:
> 
>>> So, in the new interface, how should I handle a situation that a
>>> regression is first reported on the mailing list, added to regzbot and
>>> later there's also a bug report opened for the issue?
>>
>> You will have to options: reply to the first report with a "#regzbot
>> duplicate https://bugzilla.kernel.org/show_bug.cgi?id=325423423423542";
>> or add a comment to the bugzilla ticket pointing to a report already
>> tracked by regzbot, e.g. "#regzbot duplicate
>> https://lore.kernel.org/not_relevant/msgid-423423423423423423/";
> 
> Oh, regzbot also follows bugzilla comments? Didn't know that, very nice.

Right not it only notices them. Commands in comments are not supported
yet, but will be once the partial rewrite lands.

> 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.

Ciao, Thosten