From: "Adam J. Richter" <adam@yggdrasil.com>
To: axboe@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Patch: linux-2.5.31/include/linux/blkdev.h paranethesis problem in BLK__DEFAULT_QUEUE
Date: Sun, 11 Aug 2002 00:16:59 -0700 [thread overview]
Message-ID: <20020811001659.A25279@baldur.yggdrasil.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
Hi Jens,
The following trivial fix has been in my kernel tree for
ages. It is need for the C compiler to compile statements like
the following, which I use in my version of loop.c:
BLK_DEFAULT_QUEUE(MAJOR_NR)->queuedata = NULL;
Could you please apply it to your tree and forward it to
Linus (or let me know if you'd prefer to handle it some other way).
--
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
[-- Attachment #2: blkdev.patch --]
[-- Type: text/plain, Size: 532 bytes --]
--- linux-2.5.31/include/linux/blkdev.h 2002-08-10 18:41:23.000000000 -0700
+++ linux/include/linux/blkdev.h 2002-08-11 00:06:37.000000000 -0700
@@ -272,7 +272,7 @@
* so as to eliminate the need for each and every block device
* driver to know about the internal structure of blk_dev[].
*/
-#define BLK_DEFAULT_QUEUE(_MAJOR) &blk_dev[_MAJOR].request_queue
+#define BLK_DEFAULT_QUEUE(_MAJOR) (&blk_dev[_MAJOR].request_queue)
extern struct sec_size * blk_sec[MAX_BLKDEV];
extern struct blk_dev_struct blk_dev[MAX_BLKDEV];
next reply other threads:[~2002-08-11 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 7:16 Adam J. Richter [this message]
2002-08-11 10:19 ` Patch: linux-2.5.31/include/linux/blkdev.h paranethesis problem in BLK__DEFAULT_QUEUE Jens Axboe
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=20020811001659.A25279@baldur.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=axboe@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).