From: Jens Axboe <axboe@suse.de>
To: Richard Pries <PriesRx@hlyw.com>
Cc: Glen Gerber <GlenG@hlyw.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace wrong structure type in mmc_ioctl() in cdrom.c
Date: Thu, 30 Nov 2000 22:21:53 +0100 [thread overview]
Message-ID: <20001130222153.A16299@suse.de> (raw)
In-Reply-To: <sa264be0.009@hlyw.com>
In-Reply-To: <sa264be0.009@hlyw.com>; from PriesRx@hlyw.com on Thu, Nov 30, 2000 at 12:45:11PM -0800
On Thu, Nov 30 2000, Richard Pries wrote:
> Jens,
>
> Please consider the following patch for the wrong type of structure
> in mmc_ioctl() in cdrom.c.
>
> Currently, mmc_ioctl() in cdrom.c is passed a cdrom_msf structure
> when ioctl() is called with CDROMREADRAW, CDROMREADMODE1, or
> CDROMREADMODE2 as its second argument. This structure does not
> provide the required buffer for reading the data, and it does not
> correspond to the structure that cdrom.h says to use with these
> ioctl() calls. This patch replaces the cdrom_msf structure with a
> cdrom_read structure (as specified in cdrom.h). Preliminary tests
> indicate that this patch works for both IDE and SCSI drives.
Sure I bet it works, but you just broke all the programs that currently
use any of the above ioctls. I've known about this for years... You
can do all that you want with cdrom_msf, it's just more hassle. For
2.5 I'll introduce newer variants of the above ioctls and keep them as-is
for compatability, tossing them out is not an option.
I will take a patch that corrects the comment though!
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-11-30 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sa264be0.009@hlyw.com>
2000-11-30 21:21 ` Jens Axboe [this message]
2000-11-30 20:45 [PATCH] Replace wrong structure type in mmc_ioctl() in cdrom.c Richard Pries
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=20001130222153.A16299@suse.de \
--to=axboe@suse.de \
--cc=GlenG@hlyw.com \
--cc=PriesRx@hlyw.com \
--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