mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: torvalds@transmeta.com
Cc: ankry@mif.pg.gda.pl, axboe@suse.de, linux-kernel@vger.kernel.org,
	pat@it.com.au, tfries@umr.edu
Subject: Re: PATCH: linux-2.5.1-pre7/drivers/block/xd.c compilation fix (version 2)
Date: Sat, 8 Dec 2001 22:06:57 -0800	[thread overview]
Message-ID: <200112090606.WAA07320@adam.yggdrasil.com> (raw)

>> 	Linus, if nobody says otherwise, I recommend that you apply
>> this patch.

>Well, I already applied your previous one, in fact, and it's in the
>just-uploaded pre8 kernel.

	Thanks!

>Mind verifying that and sending the incremental update?

	No problem.  I have attached the one line addition below.

>Btw, do you actually _have_ a machine that uses the xd driver, or was this
>patch done just out of some perverse joy in theoretical retrocomputing?

	Years ago, I submitted a patch to allow configuration of
the kernel with "./configure", which would configure every driver as
a module, aside from compiling in the initial ramdisk and the initial
ramdisk's filesystem.  I haven't configured a kernel for years; the
boot scripts and hot plugging software do that.  The same binary
build of the kernel can run on all of my x86 hardware.

	That is why I know that 92 files failed to compile on x86 in
2.5.1-pre7, and largely why I care about fixing xd.c.

	Anyhow, thanks for asking.  By the way, if you have any interest
in integrating my "./configure" functionality now, I would be happy to
clean it up and resubmit it.  (It is mostly a patch to scripts/Configure.)

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."


--- linux-2.5.1-pre8/drivers/block/xd.c	Sat Dec  8 21:29:50 2001
+++ linux/drivers/block/xd.c	Sat Dec  8 20:19:54 2001
@@ -287,6 +287,7 @@
 		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;

             reply	other threads:[~2001-12-09  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09  6:06 Adam J. Richter [this message]
2001-12-09  7:00 ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-12-09  4:42 Adam J. Richter
2001-12-09  4:59 ` Linus Torvalds
2001-12-09 18:08   ` Andrzej Krzysztofowicz

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=200112090606.WAA07320@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®