/linux-4.1.27/fs/xfs/ |
D | xfs_error.c | 96 int cleared = 0; in xfs_errortag_clearall() local 105 cleared = 1; in xfs_errortag_clearall() 116 if (loud || cleared) in xfs_errortag_clearall()
|
/linux-4.1.27/Documentation/parisc/ |
D | debugging | 32 happens when the Q bit is cleared is the CPU does not update the 37 instruction that cleared the Q bit, if you're not it points anywhere
|
/linux-4.1.27/arch/arc/include/asm/ |
D | tlb-mmu1.h | 29 ; -- jh_ex_way_set not cleared on startup
|
/linux-4.1.27/Documentation/vm/ |
D | soft-dirty.txt | 20 Internally, to do this tracking, the writable bit is cleared from PTEs 21 when the soft-dirty bit is cleared. So, after this, when the task tries to
|
D | active_mm.txt | 47 returned and cleared.
|
D | page_migration | 132 14. The old page flags are cleared to indicate that the page does
|
/linux-4.1.27/arch/metag/kernel/ |
D | tbiunexp.S | 13 OR D0Ar2,D0Ar2,D0Re0 ! Preserve bits cleared
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | pmc.txt | 40 and cleared on suspend, and restored on resume. This sleep controller 44 which will be ORed into PMCDR upon suspend, and cleared from PMCDR
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-arch.txt | 28 be cleared until the running task has called schedule(). Idle 55 an interrupt sleep, it needs to be cleared then a memory
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | fault_injection.txt | 36 this list is cleared, the server will have no knowledge of who the client 47 unlocked through the VFS as they are cleared from this list).
|
D | Exporting | 57 This is set when anonymous dentries are created, and cleared when a
|
/linux-4.1.27/drivers/net/ethernet/3com/ |
D | typhoon.c | 489 u32 cleared; in typhoon_process_response() local 492 cleared = le32_to_cpu(indexes->respCleared); in typhoon_process_response() 494 while(cleared != ready) { in typhoon_process_response() 495 resp = (struct resp_desc *)(base + cleared); in typhoon_process_response() 505 if(unlikely(cleared + len > RESPONSE_RING_SIZE)) { in typhoon_process_response() 506 wrap_len = cleared + len - RESPONSE_RING_SIZE; in typhoon_process_response() 507 len = RESPONSE_RING_SIZE - cleared; in typhoon_process_response() 532 typhoon_inc_resp_index(&cleared, count); in typhoon_process_response() 535 indexes->respCleared = cpu_to_le32(cleared); in typhoon_process_response() 1630 volatile __le32 * cleared, int budget) in typhoon_rx() argument [all …]
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-bus-platform | 11 driver_override) and may be cleared with an empty string
|
D | sysfs-bus-amba | 11 be cleared with an empty string (echo > driver_override).
|
D | sysfs-firmware-gsmi | 44 cleared.
|
D | sysfs-firmware-acpi | 162 All counters can be cleared by clearing the total "sci": 194 * this is because the status bit is set even if the enable bit is cleared,
|
D | sysfs-bus-pci | 223 device can be put into D3Cold state. If it is cleared, the 274 may be cleared with an empty string (echo > driver_override).
|
D | sysfs-class-mtd | 118 bits can be cleared).
|
D | sysfs-block | 212 expects discarded blocks to be explicitly cleared. If a
|
/linux-4.1.27/Documentation/locking/ |
D | rt-mutex.txt | 67 by it (bit 0 is cleared) a competing higher priority thread can "steal" 77 doesn't already have an owner, this bit is quickly cleared if there are
|
D | rt-mutex-design.txt | 633 OK that we set that flag early, since now it is cleared.
|
/linux-4.1.27/drivers/scsi/ |
D | st.h | 38 unsigned char cleared; /* internal buffer cleared after open? */ member
|
D | st.c | 1243 (STp->buffer)->cleared = 0; in st_open() 1529 if (is_read && STp->sili && !STbp->cleared) in setup_buffering() 3764 if (STbuffer->cleared) in enlarge_buffer() 3816 st_bp->cleared = 1; in clear_buffer()
|
/linux-4.1.27/Documentation/hwmon/ |
D | w83793 | 70 sure bit 0 is cleared in the 6 values. And then set the pwm1 value to 94 If the case open alarm triggers, it will stay in this state unless cleared
|
D | adm9240 | 78 and is cleared when the temperature falls below the temp1_max_hyst value. 176 that alarm bits may be cleared on read, user-space may latch alarms and
|
D | vt1211 | 31 mode 0. In this mode, any pending interrupt is cleared 109 before the alarm is cleared (this is only true for interrupt mode 0). The
|
D | ds1621 | 86 are used internally, however, these flags do get set and cleared as the actual
|
D | f71805f | 117 alarm is cleared.
|
D | sysfs-interface | 700 automatically when read, this one sticks until cleared by
|
/linux-4.1.27/arch/mips/kvm/ |
D | 00README.txt | 25 LL/TLBP/SC. Since the TLBP instruction causes a trap the reservation gets cleared
|
/linux-4.1.27/Documentation/arm64/ |
D | tagged-pointers.txt | 19 their top byte cleared before trapping to the kernel.
|
/linux-4.1.27/Documentation/scsi/ |
D | scsi_eh.txt | 260 is cleared. 275 - scmd is removed from eh_done_q and scmd->eh_entry is cleared 290 cleared by this action. 455 - Each scmd's eh_eflags field is cleared. 460 - shost->eh_cmd_q is cleared. 462 - Each scmd->eh_entry is cleared.
|
D | ChangeLog.ncr53c8xx | 3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
|
D | ncr53c8xx.txt | 375 cleared each time the driver is loaded. The "clearprof" command 510 The profile counters are automatically cleared when the amount of
|
D | ChangeLog.sym53c8xx | 3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
|
/linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
D | 88pm860x.txt | 12 - marvell,88pm860x-irq-read-clr: inicates whether interrupt status is cleared by read
|
/linux-4.1.27/Documentation/filesystems/ |
D | automount-support.txt | 85 The expiration flag is cleared by calls to mntput. This means that expiration 117 Again, the expiration flag is cleared every time anything other than umount()
|
D | mandatory-locking.txt | 74 Note that the group-id bit is usually automatically cleared by the kernel when
|
D | xfs.txt | 303 ISGID bit is cleared if the irix_sgid_inherit compatibility sysctl
|
D | vfs.txt | 566 safe, PG_Writeback is cleared. 609 The PG_Dirty flag has been cleared and PageLocked is true.
|
D | proc.txt | 1608 effective only if the bit 2 is cleared)
|
/linux-4.1.27/Documentation/frv/ |
D | atomic-ops.txt | 58 (1) The condition CCCR.CC3 is cleared unconditionally by an exception, irrespective of whether or 96 Then it attempts to store the value back, contingent on no exception having cleared CC3 since it
|
D | kernel-ABI.txt | 60 handler. On entry to the handler, the PSR.T bit will be cleared. 241 ICC2.Z would be cleared. ICC2.C would be left unaffected. Both
|
/linux-4.1.27/Documentation/infiniband/ |
D | user_mad.txt | 125 then the open call will block until the bit is cleared (or return 127 passed to open()). The IsSM bit will be cleared when the issm file
|
/linux-4.1.27/Documentation/device-mapper/ |
D | statistics.txt | 144 If omitted, all lines are printed and then cleared. 148 If omitted, all lines are printed and then cleared.
|
/linux-4.1.27/Documentation/ |
D | nommu-mmap.txt | 53 memory and any extraneous space beyond the EOF will be cleared 123 be cleared by the kernel before being returned in accordance with the 128 to cleared physical pages when a write happens on that specific page 135 pages, and the entire map is cleared at allocation time. This can cause
|
D | md.txt | 315 be cleared. In the current implementation, a bit will be cleared 334 bitmap will be cleared when the corresponding blocks are thought 335 to be in-sync. If 'false', bits will never be cleared.
|
D | flexible-arrays.txt | 92 Individual elements in the array can be cleared with:
|
D | md-cluster.txt | 22 - schedule the bit to be cleared after a timeout.
|
D | cpu-hotplug.txt | 89 interrupts from devices. Its cleared when a cpu is brought down using
|
D | cachetlb.txt | 323 bit is cleared.
|
D | memory-barriers.txt | 2013 something up. The barrier occurs before the task state is cleared, and so sits 2312 get the lock again; it instead just waits for its task pointer to be cleared 2314 if the task pointer is cleared _before_ the next pointer in the list is read,
|
/linux-4.1.27/drivers/parport/ |
D | parport_ip32.c | 1079 unsigned int cleared; in parport_ip32_clear_epp_timeout() local 1082 cleared = 1; in parport_ip32_clear_epp_timeout() 1094 cleared = !(r & DSR_TIMEOUT); in parport_ip32_clear_epp_timeout() 1097 pr_trace(p, "(): %s", cleared ? "cleared" : "failed"); in parport_ip32_clear_epp_timeout() 1098 return cleared; in parport_ip32_clear_epp_timeout()
|
/linux-4.1.27/fs/ext4/ |
D | ialloc.c | 240 int fatal = 0, err, count, cleared; in ext4_free_inode() local 304 cleared = ext4_test_and_clear_bit(bit, bitmap_bh->b_data); in ext4_free_inode() 305 if (fatal || !cleared) { in ext4_free_inode() 333 if (cleared) { in ext4_free_inode()
|
/linux-4.1.27/Documentation/powerpc/ |
D | cpu_features.txt | 49 cur_cpu_spec[0]->cpu_features) or is cleared, respectively. These two macros
|
D | pmu-ebb.txt | 137 BESCR/EBBHR/EBBRR is cleared across fork().
|
D | eeh-pci-error-recovery.txt | 16 hardware features allow PCI bus errors to be cleared and a PCI
|
D | pci_iov_resource_on_powernv.txt | 22 cleared independently) for each PE.
|
/linux-4.1.27/Documentation/video4linux/cx2341x/ |
D | fw-calling.txt | 55 first one available (bit 0 has been cleared). The driver sets that bit, fills
|
D | fw-memory.txt | 119 interrupt mask 0x0048. If a bit is cleared in the mask, then we want our ISR to
|
/linux-4.1.27/drivers/block/drbd/ |
D | drbd_bitmap.c | 490 int cleared = 0; in bm_clear_surplus() local 507 cleared = hweight_long(*bm & ~mask); in bm_clear_surplus() 515 cleared += hweight_long(*bm); in bm_clear_surplus() 519 return cleared; in bm_clear_surplus()
|
D | drbd_actlog.c | 780 unsigned int cleared = 0; in update_sync_bits() local 802 cleared += update_rs_extent(device, BM_BIT_TO_EXT(sbnr), c, mode); in update_sync_bits() 813 if (cleared || rs_is_done) in update_sync_bits()
|
/linux-4.1.27/drivers/net/wireless/mwifiex/ |
D | README | 119 int_counter = <interrupt count, cleared when interrupt handled> 130 wakeup_tries = <wakeup device count, cleared when device awake>
|
/linux-4.1.27/Documentation/i2c/busses/ |
D | i2c-ali15x3 | 30 SMBus periodically hangs on ASUS P5A motherboards and can only be cleared
|
/linux-4.1.27/drivers/net/wireless/iwlwifi/dvm/ |
D | sta.c | 664 bool cleared = false; in iwl_clear_ucode_stations() local 677 cleared = true; in iwl_clear_ucode_stations() 682 if (!cleared) in iwl_clear_ucode_stations()
|
/linux-4.1.27/Documentation/x86/x86_64/ |
D | boot-options.txt | 22 as corrected are silently cleared by OS. 27 and CMCI. All events reported as corrected are not cleared
|
/linux-4.1.27/arch/arm/mach-tegra/ |
D | sleep-tegra30.S | 446 tst r1, #(1 << 31) @ wait until AUTO_CAL_ACTIVE is cleared 766 tst r1, #(1 << 31) @ wait until AUTO_CAL_ACTIVE is cleared
|
/linux-4.1.27/fs/ocfs2/dlm/ |
D | dlmmaster.c | 2295 int cleared = 0; in dlm_deref_lockres_handler() local 2333 cleared = 1; in dlm_deref_lockres_handler() 2339 if (cleared) in dlm_deref_lockres_handler() 2382 u8 cleared = 0; in dlm_deref_lockres_worker() local 2393 cleared = 1; in dlm_deref_lockres_worker() 2397 if (cleared) { in dlm_deref_lockres_worker()
|
/linux-4.1.27/Documentation/networking/ |
D | dns_resolver.txt | 106 This can be cleared by any process that has the CAP_SYS_ADMIN capability by
|
D | arcnet.txt | 532 the buffers are cleared to a constant value of 0x42 every time the card is 535 buffer will be cleared to 0x42 as well. This is to make it easier to figure
|
D | ip-sysctl.txt | 79 purging entries. Entries older than 5 seconds will be cleared
|
D | bonding.txt | 171 specified, the current active slave is cleared, and a new active
|
/linux-4.1.27/arch/cris/arch-v10/kernel/ |
D | entry.S | 447 ;; in R_IRQ_MASK0_RD will already be cleared. The watchdog_nmi bit 448 ;; is cleared by us however (when feeding the watchdog), which is why
|
D | head.S | 314 ;; Dont worry that the BSS is tainted. It will be cleared later.
|
/linux-4.1.27/arch/arm/kernel/ |
D | entry-header.S | 143 @ ensure bit 0 is cleared in the PC, otherwise behaviour is
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | operations.txt | 90 to be cleared before proceeding:
|
D | netfs-api.txt | 270 cleared to prevent confusion. Note that the cache will have torn down all 579 (4) When the write is complete PG_fscache_write is cleared on the page and 583 is also possible for the PG_fscache_write bit to be cleared when no write took 764 markings are cleared up.
|
D | backend-api.txt | 195 page examination when it detects PG_lock being cleared.
|
/linux-4.1.27/scripts/ |
D | spelling.txt | 213 claread||cleared 214 clared||cleared
|
/linux-4.1.27/Documentation/arm/ |
D | vlocks.txt | 77 will contain only one value that won't change once every CPU has cleared
|
/linux-4.1.27/arch/c6x/kernel/ |
D | entry.S | 121 ;; a syscall. It is cleared here, but the syscall handler
|
/linux-4.1.27/arch/arm/mach-omap2/ |
D | sleep34xx.S | 336 orreq r0, r0, #(1 << 2) @ Enable the C bit if cleared
|
/linux-4.1.27/Documentation/isdn/ |
D | README.x25 | 103 occurs, all existing X.25 connections on that link will be cleared
|
/linux-4.1.27/arch/m68k/ifpsp060/ |
D | fskeleton.S | 190 | bsun will now be re-executed but with the NaN FPSR bit cleared.
|
/linux-4.1.27/drivers/staging/comedi/ |
D | comedi_fops.c | 161 bool cleared = false; in comedi_clear_board_dev() local 166 cleared = true; in comedi_clear_board_dev() 169 return cleared; in comedi_clear_board_dev()
|
/linux-4.1.27/arch/cris/arch-v10/ |
D | README.mm | 215 The kernels own page-directory is the swapper_pg_dir, cleared in paging_init,
|
/linux-4.1.27/fs/affs/ |
D | Changes | 26 last allocated block is not cleared. Well,
|
/linux-4.1.27/arch/arc/ |
D | Kconfig | 407 The counters can be cleared via Debugfs as well
|
/linux-4.1.27/drivers/scsi/aic7xxx/ |
D | aic79xx.seq | 109 * ENSELO is cleared by a SELDO, so we must test for SELDO 574 * be cleared when the message is acted on. 1312 * busfree status was cleared at the 1509 * (SG_CACHE_AVAIL would have been cleared in 1657 * Ensure that any FIFO contents are cleared out and the 2196 * nonpackreq if we've cleared out the FIFOs and handled any
|
D | aic7xxx.seq | 174 * and SELDO will be cleared in that case. 1071 * Keep HHADDR cleared for future, 32bit addressed 1145 * HDMAEN cannot be cleared. The fix used here is to drain 1446 * instead of being killed by SCSIEN getting cleared.
|
/linux-4.1.27/arch/s390/kernel/ |
D | entry.S | 295 jg s390_handle_mcck # TIF bit will be cleared by handler 594 brasl %r14,s390_handle_mcck # TIF bit will be cleared by handler
|
/linux-4.1.27/arch/m68k/fpsp040/ |
D | gen_except.S | 322 | are set by a previous instruction and not cleared by
|
D | round.S | 36 | a0 is preserved and the g-r-s bits in d0 are cleared.
|
/linux-4.1.27/Documentation/development-process/ |
D | 3.Early-stage | 187 public mailing list. The posting of code which has not been cleared for
|
/linux-4.1.27/Documentation/crypto/ |
D | asymmetric-keys.txt | 267 cleared, except for data, datalen and quotalen [see
|
D | descore-readme.txt | 275 the rightmost two bits are usually cleared so the lower byte can be used
|
/linux-4.1.27/Documentation/s390/ |
D | 3270.txt | 222 PA2 causes the log area to be cleared. If output awaits, it is then
|
/linux-4.1.27/Documentation/ia64/ |
D | fsys.txt | 99 - PSR.be = cleared to zero (i.e., little-endian byte order is in effect)
|
/linux-4.1.27/Documentation/power/ |
D | freezing-of-tasks.txt | 28 it loop until PF_FROZEN is cleared for it. Then, we say that the task is
|
D | runtime_pm.txt | 239 this flag is cleared; this is the error code returned by the failing
|
/linux-4.1.27/Documentation/serial/ |
D | driver | 208 buffer is cleared.
|
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/ |
D | hub.fuc | 398 // to hang with STATUS=0x00000007 until it's cleared.. fbcon can
|
/linux-4.1.27/Documentation/trace/ |
D | events.txt | 248 cleared as a group by writing a filter expression into the filter file
|
D | ftrace.txt | 125 or cleared by writing a "1" or "0" respectively into the
|
/linux-4.1.27/drivers/net/wireless/iwlegacy/ |
D | common.c | 2224 bool cleared = false; in il_clear_ucode_stations() local 2233 cleared = true; in il_clear_ucode_stations() 2238 if (!cleared) in il_clear_ucode_stations()
|
/linux-4.1.27/mm/ |
D | Kconfig | 545 it can be cleared by hands.
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | api.txt | 254 memory slot. Ensure the entire structure is cleared to avoid padding 845 corresponding bits in the flags field cleared to suppress overwriting the 886 yet and must be cleared on entry. 2100 the host and read/cleared exclusively by the guest. The guest operation of 2736 or unsupported feature bits cleared.
|
D | timekeeping.txt | 323 32-bits of the counter were cleared. Now, however, on Intel processors family
|
/linux-4.1.27/Documentation/video4linux/ |
D | v4l2-controls.txt | 571 active again and the volatile flag is cleared (so g_volatile_ctrl is no longer
|
D | vivid.txt | 547 constantly. If 'Gain, Automatic' is cleared, then the Gain control is a normal
|
D | v4l2-framework.txt | 132 that parent device it has to be cleared as well to mark that the parent is
|
/linux-4.1.27/Documentation/input/ |
D | sentelic.txt | 819 (Note that if this bit is cleared, bit 3/5 will be ineffective)
|
/linux-4.1.27/init/ |
D | Kconfig | 1723 in the latency of the free. On overflow these caches will be cleared 1733 from mmap() has it's contents cleared before it is passed to
|
/linux-4.1.27/Documentation/security/ |
D | Smack.txt | 213 file or cleared by writing "-" to the file.
|
D | keys.txt | 1157 rest will be cleared.
|
/linux-4.1.27/Documentation/cdrom/ |
D | cdrom-standard.tex | 340 corresponding capability flags will be cleared upon registration.
|
/linux-4.1.27/arch/m68k/ifpsp060/src/ |
D | pfpsp.S | 2335 mov.w %d0,FP_SRC_EX(%a6) # insert exponent with cleared sign
|
D | fpsp.S | 2336 mov.w %d0,FP_SRC_EX(%a6) # insert exponent with cleared sign
|