public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hazelton <dhazelton@enter.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: Parag Warudkar <parag.warudkar@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs
Date: Fri, 2 May 2008 19:15:37 -0400	[thread overview]
Message-ID: <200805021915.37480.dhazelton@enter.net> (raw)
In-Reply-To: <20080502180151.GD5838@cs181133002.pp.htv.fi>

On Friday 02 May 2008 14:01:51 Adrian Bunk wrote:
> On Fri, May 02, 2008 at 01:30:23PM -0400, Parag Warudkar wrote:
> > On Fri, May 2, 2008 at 12:29 PM, Daniel Hazelton <dhazelton@enter.net>
> > wrote: This is what Adrian was pointing
<snip>
>
> From what I forwarded it's clear that we have a bug somewhere in the
> kernel.
>
> And the maintainer might well be right that it's not in his driver.

This is something that can't be known without enough information from the 
person reporting the bug. From what you posted of the bugzilla entry it's 
unclear whether the reporter did post more than his simple description or 
not.

However, the point is well made and I, at least, agree. (whatever that may be 
worth - I've never managed to finish a patch for anything without seeing the 
equivalent show up here later)

> Which means to reassign the bug to the maintainer of the area this bug
> is in.

Yep. Closing it with a comment of "broken hardware" is an incorrect response. 
Doubly or trebly so if the bugzilla entry didn't contain enough information 
to even determine whether the bug was in the driver or not.

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.

  parent reply	other threads:[~2008-05-02 23:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:42 How to reduce the number of open kernel bugs Parag Warudkar
2008-05-02 15:11 ` Adrian Bunk
2008-05-02 16:29 ` Daniel Hazelton
2008-05-02 17:27   ` Andi Kleen
2008-05-02 17:40     ` Daniel Hazelton
2008-05-02 17:30   ` Parag Warudkar
2008-05-02 17:44     ` Daniel Hazelton
2008-05-02 17:48       ` Rafael J. Wysocki
2008-05-02 18:18         ` Andi Kleen
2008-05-02 23:10           ` Daniel Hazelton
2008-05-02 18:01     ` Adrian Bunk
2008-05-02 18:25       ` Parag Warudkar
2008-05-02 23:15       ` Daniel Hazelton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-02 12:42 Adrian Bunk
2008-05-03 10:13 ` SL Baur
2008-05-03 11:21   ` Adrian Bunk
2008-05-03 12:00     ` SL Baur
2008-05-03 15:43     ` Stefan Richter
2008-05-03 15:48       ` Stefan Richter
2008-05-05 18:12       ` Adrian Bunk

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=200805021915.37480.dhazelton@enter.net \
    --to=dhazelton@enter.net \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parag.warudkar@gmail.com \
    /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