linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Stef van der Made <svdmade@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Di-30 non working [bug 967]
Date: Sun, 2 Nov 2003 21:08:23 +0100	[thread overview]
Message-ID: <200311022108.23415.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <3FA55E7B.3050706@planet.nl>


On Sunday 02 of November 2003 20:43, Stef van der Made wrote:
> Dear Bartlomiej,
>
> The problem is now fully solved. I can read from the tape, use mt on the
> tape drive. Your second patch was the final missing bit.
>
> Thanks for your help, I hope that Linus will accept the patch for test10
> so that more people can enjoy the use of this tape drive with Linux.

Great.  I will send patches to Linus soon.
Thanks for testing.

--bartlomiej

Here is second necessary patch (was posted off-list previously).

 drivers/ide/ide-tape.c |    1 +
 1 files changed, 1 insertion(+)

diff -puN drivers/ide/ide-tape.c~ide-tape-chrdev-oops-fix drivers/ide/ide-tape.c
--- linux-2.6.0-test9/drivers/ide/ide-tape.c~ide-tape-chrdev-oops-fix	2003-11-02 19:25:17.356121528 +0100
+++ linux-2.6.0-test9-root/drivers/ide/ide-tape.c	2003-11-02 19:26:13.490587792 +0100
@@ -5548,6 +5548,7 @@ static int idetape_chrdev_open (struct i
 		return -ENXIO;
 	drive = idetape_chrdevs[i].drive;
 	tape = drive->driver_data;
+	filp->private_data = drive;
 
 	if (test_and_set_bit(IDETAPE_BUSY, &tape->flags))
 		return -EBUSY;

_


      reply	other threads:[~2003-11-02 20:03 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
2003-11-02 19:43       ` Stef van der Made
2003-11-02 20:08         ` Bartlomiej Zolnierkiewicz [this message]

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=200311022108.23415.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=svdmade@planet.nl \
    /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).