All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	ath11k@lists.infradead.org,  linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [regression] ath11k broken in v6.7
Date: Fri, 02 Feb 2024 13:34:37 +0200	[thread overview]
Message-ID: <87mssjt7zm.fsf@kernel.org> (raw)
In-Reply-To: <0c8e379b-91fa-4e02-8758-aeee01024c93@leemhuis.info> (Linux regression tracking's message of "Fri, 2 Feb 2024 12:29:11 +0100")

"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.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


      reply	other threads:[~2024-02-02 11:34 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
2024-02-02 11:29                   ` Linux regression tracking (Thorsten Leemhuis)
2024-02-02 11:34                     ` Kalle Valo [this message]

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=87mssjt7zm.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.