mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs
Date: Fri, 2 May 2008 18:11:34 +0300	[thread overview]
Message-ID: <20080502151134.GC5838@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <82e4877d0805020742l7d4a6ec9mc72e79aa3d242348@mail.gmail.com>

On Fri, May 02, 2008 at 10:42:21AM -0400, Parag Warudkar wrote:
> Adrian Bunk <bunk <at> kernel.org> writes:
> 
> > Maintainer:
> >
> > Yeah, in any case. I cannot fix it, since it's not a bug in the fobar
> > code. Please reopen a new bug and CC the architecture or PCI maintainer
> > or whatever person related to the bus, chipset or CPU, if you think the
> > foobar device still works. If the foobar hardware got corrupted, you
> > already know what to do...
> >
> > I am well aware that loud flames are often the only working way of
> > communication in Linux kernel development, but we mustn't communicate
> > this way with bug submitters.
> >
> 
> Actually this way of _communication_ is better because the maintainer has -

When immediately closing a new bug with a comment only consisting of 
"Your hardware is seriously broken." it's borderline whether you can 
call this "communication" - especially if the hardware works under 
Windows or with a different driver.

> a) at least seen the bug
> b) made it clear upfront that he/she is not in a position to fix it and
> c) not inflicted a huge amount of follow up work for the reporter
> while giving no hope that it will be fixed.

And gave the bug reporter (who might have spent some time on writing a 
proper bug report) the clear impression his bug reports are unwanted.

> There is not much you can do if the maintainer feels he/she can't do
> anything - apart from fixing it yourself which has its limits.
> So the best that can be done is to communicate it clearly - that
> happens in this case.
>...

He can ask for the output of "dmesg" and then reassign the bug to the 
correct people.

Different to immediately closing the bug with the comment
"Your hardware is seriously broken." this can result in the
bug actually being fixed.

> Parag

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-05-02 15:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:42 Parag Warudkar
2008-05-02 15:11 ` Adrian Bunk [this message]
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
  -- 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=20080502151134.GC5838@cs181133002.pp.htv.fi \
    --to=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

all inboxes | Powered by JetHome®