From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org, axboe@suse.de, pat@it.com.au,
tfries@umr.edu, ankry@mif.pg.gda.pl, torvalds@transmeta.com
Subject: PATCH: linux-2.5.1-pre7/drivers/block/xd.c compilation fix (version 2)
Date: Sat, 8 Dec 2001 20:42:25 -0800 [thread overview]
Message-ID: <20011208204225.A7213@adam.yggdrasil.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Per the advice of Jens Axboe, I have added one line to my
previous fix to make linux-2.5.1-pre7/drivers/block/xd.c compile
(the "&& (CURRENT->flags & REQ_CMD)" line). Here is the diff
against pristine linux-2.5.1-pre7/drivers/block/xd.c.
There is no maintainer for xd.c listed in linux/MAINTAINERS,
although I am and have been mailing to the email addresses that appear
in xd.c.
Linus, if nobody says otherwise, I recommend that you apply
this patch.
--
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
[-- Attachment #2: xd.patch --]
[-- Type: text/plain, Size: 1469 bytes --]
--- linux-2.5.1-pre7/drivers/block/xd.c Fri Dec 7 19:37:41 2001
+++ linux/drivers/block/xd.c Sat Dec 8 20:28:14 2001
@@ -121,7 +121,6 @@
static struct hd_struct xd_struct[XD_MAXDRIVES << 6];
static int xd_sizes[XD_MAXDRIVES << 6], xd_access[XD_MAXDRIVES];
static int xd_blocksizes[XD_MAXDRIVES << 6];
-static int xd_maxsect[XD_MAXDRIVES << 6];
extern struct block_device_operations xd_fops;
@@ -246,8 +245,7 @@
}
/* xd_maxsectors depends on controller - so set after detection */
- for(i=0; i<(XD_MAXDRIVES << 6); i++) xd_maxsect[i] = xd_maxsectors;
- max_sectors[MAJOR_NR] = xd_maxsect;
+ blk_queue_max_sectors(BLK_DEFAULT_QUEUE(MAJOR_NR), xd_maxsectors);
for (i = 0; i < xd_drives; i++) {
xd_valid[i] = 1;
@@ -289,16 +287,17 @@
INIT_REQUEST; /* do some checking on the request structure */
if (CURRENT_DEV < xd_drives
+ && (CURRENT->flags & REQ_CMD)
&& CURRENT->sector + CURRENT->nr_sectors
<= xd_struct[MINOR(CURRENT->rq_dev)].nr_sects) {
block = CURRENT->sector;
count = CURRENT->nr_sectors;
- switch (CURRENT->cmd) {
+ switch (rq_data_dir(CURRENT)) {
case READ:
case WRITE:
for (retry = 0; (retry < XD_RETRIES) && !code; retry++)
- code = xd_readwrite(CURRENT->cmd,CURRENT_DEV,CURRENT->buffer,block,count);
+ code = xd_readwrite(rq_data_dir(CURRENT),CURRENT_DEV,CURRENT->buffer,block,count);
break;
default:
printk("do_xd_request: unknown request\n");
next reply other threads:[~2001-12-09 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 4:42 Adam J. Richter [this message]
2001-12-09 4:59 ` Linus Torvalds
2001-12-09 18:08 ` Andrzej Krzysztofowicz
2001-12-09 6:06 Adam J. Richter
2001-12-09 7:00 ` Keith Owens
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=20011208204225.A7213@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=ankry@mif.pg.gda.pl \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pat@it.com.au \
--cc=tfries@umr.edu \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®