All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to improve PCI bug tracking?
Date: Thu, 19 Jan 2017 06:35:13 +0100	[thread overview]
Message-ID: <20170119053513.GA25889@wunner.de> (raw)
In-Reply-To: <88c6fcac-78d7-e2fd-e08f-62149b34e996@codeaurora.org>

On Wed, Jan 18, 2017 at 06:29:15PM -0500, Sinan Kaya wrote:
> On 1/18/2017 5:53 PM, Bjorn Helgaas wrote:
> > 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.
> 
> I have seen this happening on linux-scsi.
> 
> http://www.spinics.net/lists/linux-scsi/msg103272.html

Same for dri-devel@ / nouveau@lists.freedesktop.org.

Go for it.

Lukas

  reply	other threads:[~2017-01-19  5:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2017-01-19 11:16 ` Joao Pinto

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=20170119053513.GA25889@wunner.de \
    --to=lukas@wunner.de \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.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 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.