From: Andrew Morton <akpm@osdl.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Nigel Cunningham <ncunningham@linuxmail.org>,
suspend2-devel <suspend2-devel@lists.suspend2.net>,
suspend2-users <suspend2-users@lists.suspend2.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Reporting driver bugs.
Date: Tue, 26 Sep 2006 18:15:57 -0700 [thread overview]
Message-ID: <20060926181557.16a19343.akpm@osdl.org> (raw)
In-Reply-To: <4519C991.4070604@garzik.org>
On Tue, 26 Sep 2006 20:45:05 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Nigel Cunningham wrote:
> > Hi everyone.
> >
> > I've been involved in a little discussion this morning about reporting
> > driver bugs. In the past, I've tended to point people directly to the
> > driver author, but I've learnt that the preferred thing is to get people
> > to open reports on bugzilla.kernel.org.
> >
> > I'm therefore writing to ask if those of you who help with triage could
> > point people there as well.
>
> Unfortunately there is no one right answer. Some driver maintainers
> don't see the bugzilla.kernel.org entry at all; others find it useful
> for tracking purposes.
>
> At the very least, one should make sure the driver author is always CC'd
> on initial bug reports.
>
I screen all bugzilla reports and ensure that each one gets to the appropriate developer, if there is one.
next prev parent reply other threads:[~2006-09-27 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 0:25 Nigel Cunningham
2006-09-27 0:45 ` Jeff Garzik
2006-09-27 1:15 ` Andrew Morton [this message]
2006-09-27 7:32 ` Duncan Sands
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=20060926181557.16a19343.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=rjw@sisk.pl \
--cc=suspend2-devel@lists.suspend2.net \
--cc=suspend2-users@lists.suspend2.net \
/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
all inboxes | Powered by JetHome®