From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: porting howto for 2.5?
Date: Sat, 8 Dec 2001 22:26:48 +0100 (CET) [thread overview]
Message-ID: <200112082126.WAA10376@nbd.it.uc3m.es> (raw)
OK, I'm beat for the night.
io_request_lock disappeared. OK, so apparently I'm now supposed
to use the queue lock.
req->cmd is now an array. OK, so I really wanted the direction of
the req, so I used rq_data_dir, which looks at the req->flags.
But what are the flags for? I need space on a req to hold a
"sequence number". Doesn't matter if it wraps. Just has to be
valid for 10s. What is the cmd array an array OF?
buffer heads have gone! Now there are "bio"s. Boo hoo .. just
when I was really getting good with buffer_head. How do I
copy stuff to/from user space from a bio!? It seems to contain
bio_vecs.
Is there a 2.4-2.5 porting howto beginning to be developed somewhere?
Please?
How can one man do such damage in just one version increment :-)?
Peter
next reply other threads:[~2001-12-08 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 21:26 Peter T. Breuer [this message]
2001-12-11 23:57 ` Randy.Dunlap
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=200112082126.WAA10376@nbd.it.uc3m.es \
--to=ptb@it.uc3m.es \
--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®