- 01 Nov, 2002 29 commits
-
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Alan Cox authored
-
Adam Radford authored
-
Alexander Viro authored
RIP. It's not used anymore, so we kill assignments to it and the field itself. That was the last serious use of kdev_t in block drivers.
-
Alexander Viro authored
* in floppy drivers and ps2esdi - replaced with use of ->rq_disk; floppy drivers already have information about "type" part of device number - they had stored that information in floppy_open(), so all we need is a "which drive" part. And that is available from ->rq_disk. * DAC960: changed ->private_data initialization - instead of pointing it to controller (which we already have as disk->queue.queuedata) we simply store a disk number in there. That had simplified ->revalidate_disk() and allowed to kill the use of ->rq_dev in request handler.
-
Alexander Viro authored
* killed the uses of ->rq_dev in printks - several drivers.
-
Alexander Viro authored
* uses in ll_rw_blk.c and elevator.c eliminated - ->rq_disk has everything we need.
-
Alexander Viro authored
* eliminated, since we actually wanted the name, not device number (BTW, that had also killed calculation of name that used to duplicate sd.c one)
-
Alexander Viro authored
_Now_ we can clean the scsi_get_request_dev() up. Indeed, for any SCSI request we either have ->rq_dev == NODEV and ->rq_disk == NULL or ->rq_disk->private_data points to address of template in question. IOW, scsi_get_request_dev() becomes simply { struct gendisk *p = req->rq_disk; return p ? *(struct Scsi_Device_Template **)p->private_data : NULL; } and that allows to kill ->max_major, ->min_major and ->major in Scsi_Device_Template, along with the last non-trivial use of ->rq_dev.
-
Alexander Viro authored
Ditto for sg.c
-
Alexander Viro authored
Ditto for sd.c
-
Alexander Viro authored
Ditto for sr.c
-
Alexander Viro authored
Ditto for st.c
-
Alexander Viro authored
Next 5 chunks prepare cleanup of scsi_get_request_dev(). Namely, scsi_disk/scsi_cd/... get a new field - pointer to Scsi_Device_Template. It is initialized with address of that driver's template. sr.c and sd.c have disk->private_data pointing to that field (instead of pointing to entire structure). osst.c, st.c and sg.c get gendisk - allocated, but not registered (obviously) with ->private_name set in the same way. When they set ->rq_dev, they also set ->rq_disk. This chunk does it for osst.c
-
Alexander Viro authored
->open() of st and osst sets file->private_data to Scsi_Tape in question, other methods use it (same as in sg.c)
-
Alexander Viro authored
* new inlined helper: tape_name(tape) * most of TAPE_NR() uses replaced with that animal ("st%d ...", TAPE_NR(STp), ... -> "%s ...", tape_name(STp), ... )
-
Alexander Viro authored
* new inlined helper: tape_name(tape) * most of TAPE_NR() uses replaced with that animal ("osst%d ...", TAPE_NR(STp), ... -> "%s ...", tape_name(STp), ... )
-
Ivan Kokshaysky authored
- isapnp: asm/io.h is needed for inb() etc.; - sync up with 2.5.44 vmlinux.lds changes.
-
Alexander Viro authored
OK, that's my f*ckup in rd.c (not on initrd path, actually) + couple of f*ckups from Pat (mine: forgot to bump ->bd_count in rd_open(), Pat's: dropped reference to gendisk on del_gendisk(), resulting in use of kfree'd object + tried to remove a symlink that didn't exit). This fixes these. It also changes order of blkdev_put()/del_gendisk() in initrd_release() - better safe than sorry. It got initrd working on my boxen...
-
http://jfs.bkbits.net/linux-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Dave Kleikamp authored
The posix acls are implemented as extended attributes and are compatible with ext2/ext3 posix acls.
-
Dave Kleikamp authored
into shaggy.austin.ibm.com:/shaggy/bk/jfs-2.5
-
- 31 Oct, 2002 11 commits
-
-
http://lia64.bkbits.net/to-linus-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://linux-bt.bkbits.net/bt-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
David Mosberger authored
-
Erich Focht authored
Dear David, please find attached two patches for the latest 2.5.44-ia64. They fix some problems and simplify things a bit. remove_nodeid-2.5.44.patch: This comes from Kimi. In 2.5.44 we suddenly had two definitions for numa_node_id(), one was IA64 specific (local_cpu_data->nodeid) while the other one is now platform independent: __cpu_to_node(smp_processor_id()). After some discussions we decided to remove the nodeid from the local_cpu_data and keep the definition of all other platforms. With using the cpu_to_node_map[] we are also faster when doing multiple lookups, as all node ids come in a single cache line (which is not bounced around, as it's content is only read). ia64_topology_fixup-2.5.44.patch: I'm following here the latest fixup for i386 from Matthew Dobson. The __node_to_cpu_mask() macro now accesses an array which is initialized after the ACPI CPU discovery. It also simplifies __node_to_first_cpu(). A compiler warning has been fixed, too. Please apply these to your kernel tree.
-
David Mosberger authored
-
Robert Love authored
The hyper-threading in /proc/cpuinfo patch introduced a compile warning under UP. Fixed thus.
-
Luca Barbieri authored
This trivial patch causes the TLS to be cleared on execve (code is in flush_thread). This is necessary to avoid ESRCH errors when set_thread_area is asked to choose a free TLS entry after several nested execve's. The LDT also has a similar problem, but it is less serious because the LDT code doesn't scan for free entries. I'll probably send a patch to fix this too, unless there is something important relying on this behavior.
-
bk://cifs.bkbits.net/linux-2.5cifsLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
John Levon authored
As per comment: restoring APIC_LVTPC can trigger an apic error because the delivery mode and vector nr combination can be illegal. That's by design: on power on apic lvt contain a zero vector nr which are legal only for NMI delivery mode. So inhibit apic err before restoring lvtpc
-
John Levon authored
We need to use u64 because the future 64-bit ports can theoretically return the same value for two different dentries, as pointed out by Ulrich Weigand. The patch also changes return value of the syscall to give length of data copied, needed for valgrind support (this bit is by Philippe Elie). Note this is not a complete fix for mixed 32/64: userspace needs to figure out the kernel pointer size when reading from the buffer. But that's another fix... NOTE! any oprofile users will need to upgrade after this goes in, and the user-space equivalent is checked into CVS. Sorry for the inconvenience
-
Andrew Morton authored
Companion to the previous patch: all the support needed for non-ia32 architectures.
-