From: rct@gherkin.frus.com (Bob_Tracy)
To: linux-kernel@vger.kernel.org
Subject: various 2.5.4 problems
Date: Tue, 12 Feb 2002 07:40:54 -0600 (CST) [thread overview]
Message-ID: <m16adB0-0005khC@gherkin.frus.com> (raw)
Haven't seen any discussion of these yet, so here goes the latest
laundry list. Patches not offered here: I'm in way over my head,
but you'll note that doesn't keep me from mentioning things I've
explored :-).
linux/drivers/usb/storage/datafab.c:
linux/drivers/usb/storage/jumpshot.c:
several instances of "memcpy(... sg[sg_idx].address ..." where
"address" is no longer a valid structure member. I saw
similar things in the 2.5.4 patch suggesting that a fix
might be "memcpy(... page_address(sg[sg_idx].page) ..."
linux/drivers/sound/dmabuf.c:
linux/drivers/char/drm/i810_dma.c:
linux/drivers/video/vesafb.c:
virt_to_bus() has gone bye-bye. Compiler suggests using
the pci_map routines in this context. Don't know how to
proceed.
linux/drivers/md/lvm.c:
A couple of things here. lvm_get_blksize() should be
block_size(). This one has been mentioned before.
The other problem is a reference to current->sigpending.
A possible fix is to replace "if (current->sigpending != 0)"
with "if (signal_pending(current))".
linux/arch/i386/kernel/process.c:
linux/include/asm-i386/processor.h:
Patch set previously provided by someone else for returning
saved PC of a blocked thread.
linux/fs/intermezzo/super.c:
read_super --> get_sb conversion not done for this filesystem.
This one is more difficult than the patches I saw for other
filesystems, because presto_read_super() calls
fstype->read_super().
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
reply other threads:[~2002-02-12 13:41 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=m16adB0-0005khC@gherkin.frus.com \
--to=rct@gherkin.frus.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