From: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
To: linux-kernel@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Pointers/Info on 2.5 buffer management changes pls.
Date: Sun, 13 Jul 2003 15:37:53 +0100 [thread overview]
Message-ID: <200307131537.53343.ruth@ivimey.org> (raw)
Folks,
Bartlomiej has bullied me into trying to bring the ataraid driver into the 2.5
world. I have so far created suitable build files and have started to look
into the code changes. I have looked through the mail archives but it is very
hard to find the right thing. So I would like to check:
1. the old code uses MINOR(bh->b_rdev) to get the minor number of the
ataraid device. Can I use minor(bh->b_bdev->bd_inode->i_rdev) to replace
that?
[I am tempted to create an inline fn buffer_to_minor() for this purpose and
put it in ataraid.h.]
2. the old code, in split_request, writes to b_rsector (2.4: the real sector
on the disk) which has no obvious equivalent in 2.5. Can someone point me to
a suitable file or email that I can use to resolve this?
Any other pointers accepted.
Thanks
Ruth
--
Engineer, Author and Webweaver
reply other threads:[~2003-07-13 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200307131537.53343.ruth@ivimey.org \
--to=ruth.ivimey-cook@ivimey.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--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
all inboxes | Powered by JetHome®