/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-dev | 17 dynamically created and destroyed as devices enter and
|
D | sysfs-bus-fcoe | 30 discovery and login. The FCoE Controller is destroyed by
|
/linux-4.1.27/drivers/gpu/drm/radeon/ |
D | radeon_vce.c | 542 bool destroyed = false, created = false, allocated = false; in radeon_vce_cs_parse() local 557 if (destroyed) { in radeon_vce_cs_parse() 610 destroyed = true; in radeon_vce_cs_parse() 656 if ((!r && destroyed) || (r && allocated)) { in radeon_vce_cs_parse()
|
/linux-4.1.27/fs/nilfs2/ |
D | Kconfig | 8 destroyed just a few seconds ago. Since this file system can keep
|
/linux-4.1.27/drivers/staging/android/ |
D | sync.h | 98 bool destroyed; member
|
D | sync.c | 89 obj->destroyed = true; in sync_timeline_destroy()
|
/linux-4.1.27/arch/m68k/fpsp040/ |
D | x_store.S | 106 | a0 -> destroyed 107 | a1 -> destroyed
|
/linux-4.1.27/drivers/infiniband/hw/nes/ |
D | nes_verbs.h | 173 u16 destroyed:1; member
|
D | nes_cm.c | 3098 if ((issue_flush) && (nesqp->destroyed == 0)) { in nes_cm_disconn_true() 3788 if (nesqp->destroyed) in cm_event_connected()
|
D | nes_verbs.c | 1472 nesqp->destroyed = 1; in nes_destroy_qp()
|
/linux-4.1.27/Documentation/i2c/ |
D | instantiating-devices | 50 The devices will be automatically unbound and destroyed when the I2C bus 185 destroyed automatically when the driver which detected them is removed, 186 or when the underlying I2C bus is itself destroyed, whichever happens
|
/linux-4.1.27/drivers/scsi/isci/ |
D | remote_device.c | 1414 int destroyed; in isci_remote_device_resume_from_abort() local 1424 destroyed = sci_remote_node_context_is_being_destroyed(&idev->rnc); in isci_remote_device_resume_from_abort() 1425 if (!destroyed) in isci_remote_device_resume_from_abort() 1430 if (!destroyed && (status == SCI_SUCCESS)) in isci_remote_device_resume_from_abort()
|
/linux-4.1.27/Documentation/filesystems/configfs/ |
D | configfs.txt | 24 destroyed in kernel, the kernel controls the lifecycle of the sysfs 28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at 64 When an item needs to be destroyed, remove it with rmdir(2). An 65 item cannot be destroyed if any other item has a link to it (via 110 Items are created and destroyed inside a config_group. A group is a
|
/linux-4.1.27/Documentation/networking/ |
D | nf_conntrack-sysctl.txt | 43 active, the conntrack will only be destroyed after the event was
|
D | ppp_generic.txt | 70 destroyed. For example, the ppp_async channel code calls this when
|
D | ip-sysctl.txt | 358 If this number is exceeded time-wait socket is immediately destroyed
|
/linux-4.1.27/Documentation/x86/ |
D | tlb.txt | 6 destroyed and must be refilled later, at some cost.
|
/linux-4.1.27/Documentation/filesystems/ |
D | dlmfs.txt | 57 destroyed and locks within them accessed.
|
D | nilfs2.txt | 7 destroyed just a few seconds ago. Since NILFS2 can keep consistency
|
D | spufs.txt | 430 descriptor is closed, the logical SPU context is destroyed.
|
D | relay.txt | 449 The channel and its associated buffers are destroyed when there are no
|
/linux-4.1.27/Documentation/RCU/ |
D | rcu.txt | 6 item being destroyed, and one that actually carries out the destruction.
|
/linux-4.1.27/scripts/ |
D | spelling.txt | 315 destoryed||destroyed 317 destroied||destroyed
|
/linux-4.1.27/Documentation/security/ |
D | keys-request-key.txt | 48 destroyed. The kernel interface returns a pointer directly to the key, and
|
D | keys.txt | 1290 when it is being destroyed. 1351 construction record is destroyed by this action and the authorisation key
|
/linux-4.1.27/Documentation/driver-model/ |
D | devres.txt | 199 when it is released or destroyed (removed and freed) - no reference
|
/linux-4.1.27/Documentation/ |
D | module-signing.txt | 240 private key must be either destroyed or moved to a secure location and not kept
|
D | vme_api.txt | 233 executed, reused and destroyed.
|
D | kobject.txt | 34 what happens to the kobject when it is created and destroyed.
|
D | DMA-API.txt | 583 result in data corruption up to destroyed filesystems.
|
D | CodingStyle | 586 environment they are created and destroyed in should always have
|
/linux-4.1.27/Documentation/frv/ |
D | kernel-ABI.txt | 106 SCR2 MMU Save for EAR0 (destroyed by icache insns
|
/linux-4.1.27/Documentation/usb/ |
D | persist.txt | 48 controllers. Result: all the power sessions are destroyed and again
|
/linux-4.1.27/Documentation/hid/ |
D | uhid.txt | 76 If you close() the fd, the device is automatically unregistered and destroyed
|
D | hid-transport.txt | 241 destroyed them via hid_destroy_device().
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | mmu.txt | 160 unpinned it will be destroyed. 197 page cannot be destroyed. See role.invalid.
|
/linux-4.1.27/Documentation/sysctl/ |
D | kernel.txt | 777 shared memory segments are automatically destroyed when their attach 788 without users and with a dead originative process will be destroyed.
|
/linux-4.1.27/Documentation/fb/ |
D | matroxfb.txt | 307 pretty effects on screen. Device was not destroyed during tests. :-)
|
/linux-4.1.27/Documentation/power/ |
D | swsusp.txt | 295 read back into memory the temporary key is destroyed which simply
|
/linux-4.1.27/Documentation/cgroups/ |
D | unified-hierarchy.txt | 112 controller states are destroyed asynchronously and controllers may
|
D | cgroups.txt | 646 that is being created/destroyed (and hence has no sub-cgroups).
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | backend-api.txt | 633 cache has been destroyed and deallocated. This will allow continuation
|
/linux-4.1.27/Documentation/vm/ |
D | unevictable-lru.txt | 196 condition is keeping them unevictable. If an unevictable region is destroyed,
|
/linux-4.1.27/net/netfilter/ |
D | Kconfig | 125 the flow-stop time (once it has been destroyed) via Connection
|
/linux-4.1.27/Documentation/video4linux/ |
D | v4l2-framework.txt | 312 Don't forget to cleanup the media entity before the sub-device is destroyed:
|