public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Holzrichter, Bruce" <bruce.holzrichter@monster.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.5pre1 /drivers/block/rd.c using nr_sectors
Date: Mon, 18 Feb 2002 08:01:29 +0100	[thread overview]
Message-ID: <20020218070129.GA25111@suse.de> (raw)
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C01101F1C@nocmail.ma.tmpw.net>
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C01101F1C@nocmail.ma.tmpw.net>

On Fri, Feb 15 2002, Holzrichter, Bruce wrote:
> Not sure if your the one to contact, but compiling 2.5.5pre1 errored out
> compiling the ramdisk driver in /drivers/block/rd.c because it is still
> using bi_end_io with the nr_sectors Argument.  I simply removed the
> nr_sectors arg to make the kernel compile past that point.  I don't know if
> that's the right route to go, but wanted to let someone know. 

That's the right fix

-- 
Jens Axboe


      reply	other threads:[~2002-02-18  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 22:07 2.5.5pre1 /drivers/block/rd.c using nr_sectors Holzrichter, Bruce
2002-02-18  7:01 ` Jens Axboe [this message]

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=20020218070129.GA25111@suse.de \
    --to=axboe@suse.de \
    --cc=bruce.holzrichter@monster.com \
    --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