linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* How to improve PCI bug tracking?
@ 2017-01-18 22:53 Bjorn Helgaas
  2017-01-18 23:29 ` Sinan Kaya
  2017-01-19 11:16 ` Joao Pinto
  0 siblings, 2 replies; 4+ messages in thread
From: Bjorn Helgaas @ 2017-01-18 22:53 UTC (permalink / raw)
  To: linux-pci; +Cc: linux-kernel

I want to improve PCI bug tracking.  It feels like our bugs don't get
the attention they need, and I'm soliciting ideas for how to improve
this.

Current situation:

  - People often report bugs via email to linux-pci.  I think this
    is good because everybody can see it.

  - Even after an email report, I often request a bugzilla because
    (1) it helps keep things from being forgotten, (2) it's a
    convenient place to store bulky data, and (3) I like to have a
    bugzilla URL to include in the changelog of a patch that fixes the
    bug.

  - Sometimes people open a bugzilla directly.  I get email about
    these (along with one or two other people), but this is sort of a
    problem because linux-pci never sees it, sometimes I miss it, and
    things tend to languish.

  - Discussion on a bugzilla is only seen by people listed in the
    bugzilla, not on linux-pci.

I'm contemplating changing this so the bugzilla mail would also go to
linux-pci.

Any objections or alternate suggestions?

Bjorn

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-01-19 11:16 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-01-18 22:53 How to improve PCI bug tracking? Bjorn Helgaas
2017-01-18 23:29 ` Sinan Kaya
2017-01-19  5:35   ` Lukas Wunner
2017-01-19 11:16 ` Joao Pinto

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).