From: Kalle Valo <kvalo@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: ath11k@lists.infradead.org,
Linux regressions mailing list <regressions@lists.linux.dev>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] ath11k broken in v6.7
Date: Fri, 02 Feb 2024 12:45:37 +0200 [thread overview]
Message-ID: <87r0hvta9a.fsf@kernel.org> (raw)
In-Reply-To: <ccbb3aeb-daa1-49ba-b729-964bd97748bc@leemhuis.info> (Thorsten Leemhuis's message of "Fri, 2 Feb 2024 09:14:55 +0100")
Thorsten Leemhuis <regressions@leemhuis.info> 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
next prev parent reply other threads:[~2024-02-02 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 20:47 [regression] ath11k broken in v6.7 Kalle Valo
2024-01-19 6:34 ` Kalle Valo
2024-01-19 7:50 ` Kalle Valo
2024-01-22 7:36 ` Kalle Valo
2024-01-22 8:03 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-22 8:24 ` Kalle Valo
2024-01-22 10:24 ` Thorsten Leemhuis
2024-01-29 11:33 ` Kalle Valo
2024-02-02 8:14 ` Thorsten Leemhuis
2024-02-02 10:45 ` Kalle Valo [this message]
2024-02-02 11:29 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-02 11:34 ` Kalle Valo
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=87r0hvta9a.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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.