From: Arjan van de Ven <arjan@infradead.org>
To: "Lasse Kärkkäinen / Tronic" <tronic+bpsk@trn.iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Libata, bug 5700.
Date: Sat, 28 Jan 2006 13:24:50 +0100 [thread overview]
Message-ID: <1138451090.2993.14.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <43DB5BE5.8050900@trn.iki.fi>
On Sat, 2006-01-28 at 13:56 +0200, Lasse Kärkkäinen / Tronic wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=5700
>
> I reported this bug a while back, but it hasn't received any feedback.
> Jeff Garzik didn't respond to the email that I sent to him either. What's up?
While not responding to mails is not nice, demanding a response isn't
nice either. Jeff Garzik or any other kernel developer has no support
obligation to you in any way or form.
Maybe think about if there's more information you can supply to make it
easier for the developers to diagnose (this is the most common reason
bugs aren't looked at, just plain not enough info to even begin thinking
about it)... or look at the code yourself, or try to find where this
behavior started, or .. or ...
next prev parent reply other threads:[~2006-01-28 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 11:56 Libata, bug 5700 Lasse Kärkkäinen / Tronic
2006-01-28 12:24 ` Arjan van de Ven [this message]
2006-01-28 12:36 ` Pekka Enberg
2006-02-01 2:44 ` Tejun Heo
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=1138451090.2993.14.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tronic+bpsk@trn.iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).