All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Martin A. Brooks" <martin@jtrix.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre4 compile error - pd.c
Date: Fri, 30 Nov 2001 10:01:53 +0100	[thread overview]
Message-ID: <20011130100153.S16796@suse.de> (raw)
In-Reply-To: <20011130092347.L16796@suse.de> <4199.10.119.8.1.1007110697.squirrel@extranet.jtrix.com>
In-Reply-To: <4199.10.119.8.1.1007110697.squirrel@extranet.jtrix.com>

On Fri, Nov 30 2001, Martin A. Brooks wrote:
> 
> > Please try this diff.
> 
> That seems to fix that error, but I now get a (possibly related) error
> elsewhere.
> 
> 
> gcc -D__KERNEL__ -I/home/martin/kernel-a-day-club/linux/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=i686    -c -o xd.o xd.c
> xd.c: In function `xd_geninit':
> xd.c:250: `max_sectors' undeclared (first use in this function)
> xd.c:250: (Each undeclared identifier is reported only once
> xd.c:250: for each function it appears in.)
> make[3]: *** [xd.o] Error 1

max_sectors has been moved into the queue. So when you did this before

max_sectors[dev indexing] = max_sectors_in_request

you now do

q = blk_get_queue(dev);
blk_queue_max_sectors(max_sectors_in_request);

-- 
Jens Axboe


  reply	other threads:[~2001-11-30  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30  8:06 2.5.1-pre4 compile error - pd.c Martin A. Brooks
2001-11-30  8:23 ` Jens Axboe
2001-11-30  8:58   ` Martin A. Brooks
2001-11-30  9:01     ` Jens Axboe [this message]
2001-11-30  9:08       ` Martin A. Brooks

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=20011130100153.S16796@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@jtrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.