ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Lukas Wunner <lukas@wunner.de>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: users@kernel.org, ksummit@lists.linux.dev
Subject: Re: kernel.org tooling update
Date: Tue, 16 Dec 2025 12:33:16 -0800	[thread overview]
Message-ID: <2ffa25e5-ef7c-4285-925c-3f698089bf28@oss.qualcomm.com> (raw)
In-Reply-To: <aUGHHFWe_CFuOnRJ@wunner.de>

On 12/16/2025 8:21 AM, Lukas Wunner wrote:
> [cc += Bjorn, start of thread is here:
> https://lore.kernel.org/ksummit/20251209-roaring-hidden-alligator-068eea@lemur/
> ]
> 
> On Tue, Dec 09, 2025 at 11:48:24PM -0500, Konstantin Ryabitsev wrote:
>> ### Bugzilla
>>
>> It may be time to kill bugzilla:
>>
>>     - despite periodic "we're not dead yet" emails, it doesn't appear very
>>       active
>>     - the upgrade path to 6.0 is broken for us due to bugzilla abandoning the
>>       5.2 development branch and continuing with 5.1
>>     - question remains with what to replace bugzilla, but it's a longer
>>       discussion topic that I don't want to raise here; it may be a job for
>>       the bugspray bot that can extend the two-way bridge functionality to
>>       multiple bug tracker frameworks
> 
> The PCI subsystem relies heavily on bugzilla to track issues,
> collect dmesg/lspci output from reporters and furnish them with
> debug or test patches.
> 
> The SOP when issues are reported on the mailing list without
> sufficient information is to ask the reporter to open a bugzilla
> issue and attach full dmesg and lspci -vvv output for analysis.
> 
> If bugzilla is deprecated, we'll need at least a way to exchange
> files with reporters.  Preferably on kernel.org infrastructure
> to be independent from 3rd parties.  A way to communicate with
> reporters outside the mailing list is also useful to prevent
> spamming linux-pci@vger.kernel.org with messages relevant only
> to a single issue or system.
> 
> All the information now recorded in bugzilla should continue
> to be available indefinitely so that Link: tags in commits
> continue to work.  It's not uncommon to have to dig in old
> bugzilla entries in order to understand the motivation for
> a particular code section that was introduced years earlier.

At least some of the wireless maintainers also use bugzilla.
The ath11k & ath12k drivers have guidance in the wireless wiki:
https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath11k/bugreport.html
https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath12k/bugreport.html

So we would also want this or a similar service to be maintained.

/jeff


  reply	other threads:[~2025-12-16 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10  4:48 Konstantin Ryabitsev
2025-12-10  8:11 ` Mauro Carvalho Chehab
2025-12-10 13:30 ` Thorsten Leemhuis
2025-12-11  3:04   ` Theodore Tso
2025-12-12 23:48   ` Stephen Hemminger
2025-12-12 23:54     ` Randy Dunlap
2025-12-16 16:21 ` Lukas Wunner
2025-12-16 20:33   ` Jeff Johnson [this message]
2025-12-17  0:47     ` Mario Limonciello
2025-12-18 13:37       ` Jani Nikula
2025-12-18 14:09         ` Mario Limonciello

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=2ffa25e5-ef7c-4285-925c-3f698089bf28@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=helgaas@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=lukas@wunner.de \
    --cc=users@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox