All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: suspend2-devel <suspend2-devel@lists.suspend2.net>,
	suspend2-users <suspend2-users@lists.suspend2.net>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Reporting driver bugs.
Date: Wed, 27 Sep 2006 10:25:45 +1000	[thread overview]
Message-ID: <1159316745.5341.5.camel@nigel.suspend2.net> (raw)

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.

Thanks, and thanks for all your help!

Nigel


             reply	other threads:[~2006-09-27  0:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  0:25 Nigel Cunningham [this message]
2006-09-27  0:45 ` Reporting driver bugs Jeff Garzik
2006-09-27  1:15   ` Andrew Morton
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=1159316745.5341.5.camel@nigel.suspend2.net \
    --to=ncunningham@linuxmail.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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 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.