Andreas Kling 2c72d495a3 Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage ... I believe this to be safe, as the main thing that LockRefPtr provides over RefPtr is safe copying from a shared LockRefPtr instance. I've inspected the uses of RefPtr<PhysicalPage> and it seems they're all guarded by external locking. Some of it is less obvious, but this is an area where we're making continuous headway.		2022-08-24 18:35:41 +02:00
..
ATA	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
NVMe	Kernel: Use RefPtr instead of LockRefPtr for PhysicalPage	2022-08-24 18:35:41 +02:00
Ramdisk	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
DiskPartition.cpp	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
DiskPartition.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
StorageController.cpp	Kernel/Storage: Add LUN address to each StorageDevice	2022-07-15 12:29:23 +02:00
StorageController.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
StorageDevice.cpp	Kernel/Storage: Remove InterfaceType enum	2022-08-14 01:09:03 +01:00
StorageDevice.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
StorageManagement.cpp	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00
StorageManagement.h	Kernel: Make self-contained locking smart pointers their own classes	2022-08-20 17:20:43 +02:00