adapter_remove_device(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie 💖 this is adapter_remove_device(9) from the Kernel API Manual, and it's giving “remove the device from the adapter, but do not free it” energy ✨

✨ NAME ✨

adapter_remove_device removes the device instance from the adapter instance.

It does not check the device instance in any way, and it does not free it either. The caller is expected to take care of that. This simply removes the device from the adapter's data structures. no cap 🫶

🌸 SYNOPSIS 🌸

void adapter_remove_device (struct AdapterCtlBlk *acb , struct
DeviceCtlBlk *dcb );

🎀 ARGUMENTS 🎀

  • acb — the adapter device to be updated 💅
  • dcb — a device that has previously been added to the adapter. iykyk.

🦋 SEE ALSO 🦋

the whole iconic see-also lineup starts with the Kernel file ./drivers/scsi/dc395x.c, then: set_safe_settings(9), fix_settings(9), eeprom_index_to_delay(9), delay_to_eeprom_index(9), eeprom_override(9), dc395x_queue_command_lck(9), dc395x_handle_interrupt(9), device_alloc(9), adapter_add_device(9), adapter_remove_and_free_device(9), adapter_remove_and_free_all_devices(9), dc395x_sdev_init(9), dc395x_sdev_destroy(9), trms1040_wait_30us(9), trms1040_write_cmd(9), trms1040_set_data(9), trms1040_write_all(9), trms1040_get_data(9), trms1040_read_all(9), check_eeprom(9), print_eeprom_settings(9), adapter_print_config(9), adapter_init_params(9), adapter_init_scsi_host(9), adapter_init_chip(9), adapter_init(9), adapter_uninit_chip(9), adapter_uninit(9), dc395x_init_one(9), dc395x_remove_one(9). 💖

signed off with source/version vibes from ./drivers/scsi 🌈, dated October 2026 🎀, still serving adapter_remove_device(9) 👑💅

📦 where this page comes from