Home
last modified time | relevance | path

Searched refs:destroyed (Results 1 – 45 of 45) sorted by relevance

/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-dev17 dynamically created and destroyed as devices enter and
Dsysfs-bus-fcoe30 discovery and login. The FCoE Controller is destroyed by
/linux-4.1.27/drivers/gpu/drm/radeon/
Dradeon_vce.c542 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/
DKconfig8 destroyed just a few seconds ago. Since this file system can keep
/linux-4.1.27/drivers/staging/android/
Dsync.h98 bool destroyed; member
Dsync.c89 obj->destroyed = true; in sync_timeline_destroy()
/linux-4.1.27/arch/m68k/fpsp040/
Dx_store.S106 | a0 -> destroyed
107 | a1 -> destroyed
/linux-4.1.27/drivers/infiniband/hw/nes/
Dnes_verbs.h173 u16 destroyed:1; member
Dnes_cm.c3098 if ((issue_flush) && (nesqp->destroyed == 0)) { in nes_cm_disconn_true()
3788 if (nesqp->destroyed) in cm_event_connected()
Dnes_verbs.c1472 nesqp->destroyed = 1; in nes_destroy_qp()
/linux-4.1.27/Documentation/i2c/
Dinstantiating-devices50 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/
Dremote_device.c1414 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/
Dconfigfs.txt24 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/
Dnf_conntrack-sysctl.txt43 active, the conntrack will only be destroyed after the event was
Dppp_generic.txt70 destroyed. For example, the ppp_async channel code calls this when
Dip-sysctl.txt358 If this number is exceeded time-wait socket is immediately destroyed
/linux-4.1.27/Documentation/x86/
Dtlb.txt6 destroyed and must be refilled later, at some cost.
/linux-4.1.27/Documentation/filesystems/
Ddlmfs.txt57 destroyed and locks within them accessed.
Dnilfs2.txt7 destroyed just a few seconds ago. Since NILFS2 can keep consistency
Dspufs.txt430 descriptor is closed, the logical SPU context is destroyed.
Drelay.txt449 The channel and its associated buffers are destroyed when there are no
/linux-4.1.27/Documentation/RCU/
Drcu.txt6 item being destroyed, and one that actually carries out the destruction.
/linux-4.1.27/scripts/
Dspelling.txt315 destoryed||destroyed
317 destroied||destroyed
/linux-4.1.27/Documentation/security/
Dkeys-request-key.txt48 destroyed. The kernel interface returns a pointer directly to the key, and
Dkeys.txt1290 when it is being destroyed.
1351 construction record is destroyed by this action and the authorisation key
/linux-4.1.27/Documentation/driver-model/
Ddevres.txt199 when it is released or destroyed (removed and freed) - no reference
/linux-4.1.27/Documentation/
Dmodule-signing.txt240 private key must be either destroyed or moved to a secure location and not kept
Dvme_api.txt233 executed, reused and destroyed.
Dkobject.txt34 what happens to the kobject when it is created and destroyed.
DDMA-API.txt583 result in data corruption up to destroyed filesystems.
DCodingStyle586 environment they are created and destroyed in should always have
/linux-4.1.27/Documentation/frv/
Dkernel-ABI.txt106 SCR2 MMU Save for EAR0 (destroyed by icache insns
/linux-4.1.27/Documentation/usb/
Dpersist.txt48 controllers. Result: all the power sessions are destroyed and again
/linux-4.1.27/Documentation/hid/
Duhid.txt76 If you close() the fd, the device is automatically unregistered and destroyed
Dhid-transport.txt241 destroyed them via hid_destroy_device().
/linux-4.1.27/Documentation/virtual/kvm/
Dmmu.txt160 unpinned it will be destroyed.
197 page cannot be destroyed. See role.invalid.
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt777 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/
Dmatroxfb.txt307 pretty effects on screen. Device was not destroyed during tests. :-)
/linux-4.1.27/Documentation/power/
Dswsusp.txt295 read back into memory the temporary key is destroyed which simply
/linux-4.1.27/Documentation/cgroups/
Dunified-hierarchy.txt112 controller states are destroyed asynchronously and controllers may
Dcgroups.txt646 that is being created/destroyed (and hence has no sub-cgroups).
/linux-4.1.27/Documentation/filesystems/caching/
Dbackend-api.txt633 cache has been destroyed and deallocated. This will allow continuation
/linux-4.1.27/Documentation/vm/
Dunevictable-lru.txt196 condition is keeping them unevictable. If an unevictable region is destroyed,
/linux-4.1.27/net/netfilter/
DKconfig125 the flow-stop time (once it has been destroyed) via Connection
/linux-4.1.27/Documentation/video4linux/
Dv4l2-framework.txt312 Don't forget to cleanup the media entity before the sub-device is destroyed: