public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Roger W. Brown" <bregor@anusf.anu.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Definition conflict in 2.4.19-pre?? code
Date: Wed, 5 Jun 2002 12:02:29 +0200	[thread overview]
Message-ID: <20020605100229.GX1105@suse.de> (raw)
In-Reply-To: <200206051736.45920.bregor@sf.anu.edu.au>

On Wed, Jun 05 2002, Roger W. Brown wrote:
> 
>   Hi,
> 
>       I am not able to compile 2.4 series kernels after
>   linux-2.4.19-pre1 and I don't understand how others can !
> 
>   Consider the "struct request_queue" definition in blkdev.h
> 
>   In the 2.4.19-pre1 version, the last few lines read:
>         /*
>          * Tasks wait here for free read and write requests
>          */
>         wait_queue_head_t       wait_for_requests[2];
>   };
>   and for later versions this is changed to:
>         /*
>          * Tasks wait here for free request
>          */
>         wait_queue_head_t       wait_for_request;
>   };
> 
>   yet drivers/block/ll_rw_blk.c still makes references to
>   wait_for_requests[?]  in the void blk_init_free_list()
>   and blkdev_release_request() functions and elsewhere.

Your kernel tree must be corrupted, there's no such change in later
2.4.19-pre. pre10 still uses two request wait queues.

-- 
Jens Axboe


  reply	other threads:[~2002-06-05 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  7:36 Definition conflict in 2.4.19-pre?? code Roger W. Brown
2002-06-05 10:02 ` Jens Axboe [this message]
2002-06-05 12:03   ` Roger W. Brown

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=20020605100229.GX1105@suse.de \
    --to=axboe@suse.de \
    --cc=bregor@anusf.anu.edu.au \
    --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