linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Velu Erwan <erwan@seanodes.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-ide@vger.kernel.org
Cc: Bruno Harbulot <bruno_harbulot@yahoo.co.uk>
Subject: Nobody cares about the ATIIXP troubles reported since October ?
Date: Wed, 07 Jun 2006 09:36:15 +0200	[thread overview]
Message-ID: <448681EF.1020200@seanodes.com> (raw)
In-Reply-To: <447E11F9.1030804@seanodes.com>

I've been trying since a while helping people who knows about clean 
kernel hacking to solve a bug in ATIIXP but nobody seems to be 
interested to fix this bug.
I'm always trying to help when I can (kernel but other projects too) but 
I feel quite depressed about the reaction of this list.

This sure, I'm not a kernel hacker but I do my best to help in detecting 
the trouble/propose a fix/testing but nobody care about it :/

This bugs has been reported since a while (10.10.05) and it still 
exists, even in the latest RC kernel.

Why should I do to make this bug fixed ?

  reply	other threads:[~2006-06-07  7:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 23:53 ATIIXP and libata Bruno Harbulot
2005-11-04  9:16 ` Velu Erwan
2005-11-04 10:09   ` Bartlomiej Zolnierkiewicz
2005-11-05 15:32   ` Bruno Harbulot
2005-11-04 10:17 ` Bartlomiej Zolnierkiewicz
2005-11-05 15:27   ` [PATCH] " Bruno Harbulot
2006-05-31 22:00     ` Velu Erwan
2006-06-07  7:36       ` Velu Erwan [this message]
2006-06-12 22:23         ` Nobody cares about the ATIIXP troubles reported since October ? Bruno Harbulot
2006-06-12 22:32       ` [PATCH] Re: ATIIXP and libata Randy.Dunlap
2006-06-19  8:12         ` Velu Erwan
2006-06-19 17:27           ` Randy.Dunlap
2006-06-20  8:57             ` Velu Erwan
2006-06-20 16:57               ` Randy.Dunlap
2005-12-02 10:54   ` Velu Erwan

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=448681EF.1020200@seanodes.com \
    --to=erwan@seanodes.com \
    --cc=bruno_harbulot@yahoo.co.uk \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    /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).