From: Stef van der Made <svdmade@planet.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Di-30 non working [bug 967]
Date: Sun, 02 Nov 2003 13:06:18 +0100 [thread overview]
Message-ID: <3FA4F33A.7080207@planet.nl> (raw)
In-Reply-To: <200311020054.49869.bzolnier@elka.pw.edu.pl>
Hi,
I've done some more testing and the drive is now responding to commands
:-) so we are getting more close. It however still fails to give the
status back and is busy after the first command. I've included a dmesg,
updated patch and strace as attachment to the bug report. In the dmesg I
see a oops I hope that this will help you find the problem. I also had
an oops at the first try but got lost during the cut and paste work :-(
sorry for that.
Best regards,
Stef
Bartlomiej Zolnierkiewicz wrote:
>On Sunday 02 of November 2003 00:24, Andrew Morton wrote:
>
>
>>Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>>
>>
>>>Noticed by Stuart_Hayes@Dell.com:
>>>
>>>I've noticed that, in the 2.6 (test 9) kernel, the "cmd" field (of type
>>>int) in struct request has been removed, and it looks like all of the
>>>code in ide-tape has just had a find & replace run on it to replace any
>>>instance of rq.cmd or rq->cmd with rq.flags or rq->flags.
>>>
>>>
>>Nasty.
>>
>>
>>
>
>
next prev parent reply other threads:[~2003-11-02 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 20:26 Di-30 non working [bug 967] Stef van der Made
2003-11-01 21:28 ` Bartlomiej Zolnierkiewicz
2003-11-01 23:24 ` Andrew Morton
2003-11-01 23:54 ` Bartlomiej Zolnierkiewicz
2003-11-02 12:06 ` Stef van der Made [this message]
2003-11-02 19:43 ` Stef van der Made
2003-11-02 20:08 ` Bartlomiej Zolnierkiewicz
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=3FA4F33A.7080207@planet.nl \
--to=svdmade@planet.nl \
--cc=linux-kernel@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