Search Linux Wireless

Re: [regression] ath11k broken in v6.7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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/

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

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




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux