| /linux-4.1.27/Documentation/xtensa/ |
| D | mmu.txt | 53 1. Only top level simple-bus nodes are considered
55 2. Only one (first) simple-bus node is considered
59 4. Only the first triplet in the "ranges" property is considered
|
| /linux-4.1.27/Documentation/zh_CN/ |
| D | volatile-considered-harmful.txt | 1 Chinese translated version of Documentation/volatile-considered-harmful.txt
12 Documentation/volatile-considered-harmful.txt 的中文翻译
|
| /linux-4.1.27/include/trace/events/ |
| D | compaction.h | 252 __field(unsigned int, considered)
261 __entry->considered = zone->compact_considered;
271 __entry->considered,
|
| /linux-4.1.27/Documentation/devicetree/bindings/w1/ |
| D | w1-gpio.txt | 13 - linux,open-drain: if specified, the data pin is considered in
|
| /linux-4.1.27/Documentation/power/ |
| D | power_supply_class.txt | 94 when battery considered "full"/"empty" at normal conditions. Yes, there is
109 battery considered full/empty.
115 charge when battery considered full/empty at given conditions (temperature,
156 TIME_TO_EMPTY - seconds left for battery to be considered empty (i.e.
158 TIME_TO_FULL - seconds left for battery to be considered full (i.e.
|
| D | userland-swsusp.txt | 22 reading, it is considered to be in the suspend mode. Otherwise it is
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | dm-log.txt | 8 mirrors, a region would be considered dirty/inconsistent while you
11 Once all writes are complete, the region is considered clean again.
|
| D | cache-policies.txt | 51 considered sequential it will bypass the cache. The random threshold
|
| D | dm-raid.txt | 176 of "resync" or "recover" can be considered complete.
|
| /linux-4.1.27/Documentation/ |
| D | kmemleak.txt | 78 An allocated block of memory is considered orphan if no pointer to its
82 block to a freeing function and therefore the block is considered a
88 considered orphan)
96 4. the remaining white objects are considered orphan and reported via
103 block is not considered a leak. One example is __vmalloc().
|
| D | clk.txt | 293 within the .set_rate operation of another clock. This case must be considered
297 Note that locking must also be considered when code outside of the common
299 is considered out of scope of this document.
|
| D | hwspinlock.txt | 134 Doing so is considered a bug (there is no protection against this).
142 Doing so is considered a bug (there is no protection against this).
|
| D | xz.txt | 89 Creating a limited XZ encoder may be considered if people think it is
|
| D | volatile-considered-harmful.txt | 85 variables of this type is strongly frowned upon. Jiffies is considered
|
| D | local_ops.txt | 105 the data seen by local_read across CPUs must be considered to be out of order
|
| D | stable_kernel_rules.txt | 16 be considered if they fix a notable performance or interactivity issue.
|
| D | unicode.txt | 113 Unicode practice these differences are considered font variants.
|
| D | intel_txt.txt | 195 Execution Technology (TXT)". It is considered EXPERIMENTAL and
|
| D | kernel-doc-nano-HOWTO.txt | 42 Only comments so marked will be considered by the kernel-doc scripts,
|
| D | memory-hotplug.txt | 339 A memory block under ZONE_MOVABLE is considered to be able to be offlined
|
| D | 00-INDEX | 468 volatile-considered-harmful.txt
|
| D | SubmittingPatches | 293 to security@kernel.org. For severe bugs, a short embargo may be considered
661 considered part of the summary phrase, but describe how the patch
|
| D | xillybus.txt | 70 abstraction for the data exchange is often considered too big. In those cases,
|
| D | atomic_ops.txt | 19 See Documentation/volatile-considered-harmful.txt for the complete rationale.
|
| D | memory-barriers.txt | 375 considered can then perceive. A data dependency barrier issued by the CPU
486 instruction; the barrier can be considered to draw a line in that CPU's
2433 Basically, each usage case has to be carefully considered as to whether memory
2614 This means that it must be considered that the CPU will execute its instruction
|
| D | HOWTO | 251 - Process continues until the kernel is considered "ready", the
|
| D | kernel-parameters.txt | 2095 leaving touchpad surface for touch to be considered
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | renesas,sh73a0-cpg-clocks.txt | 1 These bindings should be considered EXPERIMENTAL for now.
|
| D | renesas,r8a7740-cpg-clocks.txt | 1 These bindings should be considered EXPERIMENTAL for now.
|
| /linux-4.1.27/Documentation/s390/ |
| D | kvm.txt | 3 the interface to the module is not yet considered to remain stable. Thus, be
66 submitted as floating interrupts. The following interrupts are not considered
91 submitted for a specific cpu. The following interrupts are not considered
|
| D | monreader.txt | 154 Any received data must be considered invalid until a complete set was
|
| D | Debugging390.txt | 719 -gdwarf-2 now works it should be considered the default debugging
|
| /linux-4.1.27/Documentation/arm/Atmel/ |
| D | README | 67 + Datasheet (can be considered as covering the whole family)
107 considered as "Unstable". To be completely clear, any at91 binding can change at
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | topology.txt | 40 with bindings standardized in [1] is therefore considered invalid.
68 Any other configuration is considered invalid.
117 Any other configuration is considered invalid.
143 Any other configuration is considered invalid.
|
| D | idle-states.txt | 29 wake-up capabilities, hence it is not considered in this document).
232 Any other configuration is considered invalid.
245 idle-states node, any other configuration is considered invalid and therefore
264 SBSA,[3][4]) is considered standard on all ARM platforms and therefore
300 entry, for this idle state to be considered
332 be considered operational.
|
| D | coresight.txt | 49 source is considered to belong to CPU0.
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | sharp,ls037v7dw01.txt | 21 configured with external pulls, all the GPIOs are considered optional with holes
|
| D | simple-framebuffer.txt | 15 considered the primary node.
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | twl-familly.txt | 17 it is considered as an interrupt controller cascaded to the SoC one.
|
| /linux-4.1.27/scripts/coccinelle/misc/ |
| D | ifcol.cocci | 8 /// is not visually aligned may be considered to be in the same column.
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | vdso | 22 ABI of those symbols is considered stable. It may vary across architectures,
|
| D | sysfs-module | 23 considered stable, only the fact that they will be
|
| /linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas-memory-controllers.txt | 14 should be considered EXPERIMENTAL for now.
|
| /linux-4.1.27/Documentation/devicetree/bindings/panel/ |
| D | sharp,lq101r1sx01.txt | 8 driven by the first link (DSI-LINK1), left or even, is considered the primary
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | rcar_vin.txt | 25 be considered as each vin interface has one input port.
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | nct6683 | 40 considered too risky with this firmware and has been disabled. All limits
|
| D | it87 | 150 The IT8728F, IT8771E, and IT8772E are considered compatible with the IT8721F,
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 18 When device_type is "mdio", the following strings are also considered:
39 is considered instructive, rather than descriptive. The reg property should
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-uwb_rc-wusbhc | 18 within 'wusb_trust_timeout' ms are considered to have
|
| D | sysfs-class-devfreq | 40 less than 1 jiffy, it is considered to be 0, which means
|
| D | sysfs-class-uwb_rc | 17 this time, the device will be considered to have gone
|
| D | sysfs-bus-iio | 1236 present, output should be considered as processed with the
|
| /linux-4.1.27/Documentation/virtual/kvm/devices/ |
| D | mpic.txt | 32 For edge-triggered interrupts: Writing 1 is considered an activating
|
| /linux-4.1.27/Documentation/networking/ |
| D | x25.txt | 30 be actively considered.
|
| D | driver.txt | 6 any normal circumstances. It is considered a hard error unless
|
| D | nf_conntrack-sysctl.txt | 23 considered for connection tracking.
|
| D | operstates.txt | 47 operational state. Interface must be considered for user data as
|
| D | phonet.txt | 41 the 8-bit object identifiers. As such, Phonet can be considered as a
|
| D | udplite.txt | 208 lengths), only the first fragment needs to be considered. When using
|
| D | netdev-FAQ.txt | 149 think it has been overlooked, vs. having been considered and rejected.
|
| D | rds.txt | 232 "back-pressure" is considered a bug.
|
| D | LICENSE.qlge | 126 and can be reasonably considered independent and separate works in
|
| D | LICENSE.qlcnic | 126 and can be reasonably considered independent and separate works in
|
| D | ip-sysctl.txt | 761 settings are independent and both are considered by the kernel
1700 path. Once this threshold is exceeded, the path is considered
|
| D | rxrpc.txt | 103 to multiple services. A service may be considered the RxRPC equivalent of
|
| D | arcnet-hardware.txt | 1706 It seems that the bits are considered in reverse order. Also, you must
|
| D | bonding.txt | 355 filtering can resolve this, as only ARP traffic is considered for
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | zram.txt | 133 per-stat sysfs attributes are considered to be deprecated.
143 or zram<id>/io_stat or zram<id>/mm_stat) is considered to be deprecated.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | jfs.txt | 45 a TRIM command to the block device is considered useful.
|
| D | mandatory-locking.txt | 83 I have considered the implementations of mandatory locking available with
151 ftruncate(). truncate() and ftruncate() are considered to be "write" actions
|
| D | automount-support.txt | 105 umount(). This flag is considered incompatible with MNT_FORCE and MNT_DETACH.
|
| D | devpts.txt | 30 the mount is considered to be in the multi-instance mode and a new instance
|
| D | logfs.txt | 22 For the most part, the superblocks can be considered read-only. They
|
| D | xfs-delayed-logging-design.txt | 84 IO permanently. Hence the XFS journalling subsystem can be considered to be IO
142 concept is sound. Instead it is simply considered a "solved problem" and as
254 the log but not yet written to disk. Such log items are considered "active"
730 are entered and completed is the object considered clean.
|
| D | gfs2-glocks.txt | 181 needs to be carefully considered when interpreting the
|
| D | seq_file.txt | 164 manipulated by the other functions is considered to be completely opaque by
|
| D | xfs-self-describing-metadata.txt | 176 buffer is considered corrupt and the EFSCORRUPTED error is set appropriately.
|
| D | autofs4-mount-control.txt | 381 the descriptor corresponds to is considered a mountpoint if it is itself
|
| D | proc.txt | 653 just those considered 'most important'. The new vectors are:
1460 equivalent to discounting 50% of the task's allowed memory from being considered
|
| /linux-4.1.27/arch/mips/sibyte/ |
| D | Kconfig | 133 bool "All cache exceptions considered fatal (no recovery attempted)"
|
| /linux-4.1.27/Documentation/devicetree/bindings/c6x/ |
| D | interrupt.txt | 41 considered to have the core interrupt controller as the parent.
|
| /linux-4.1.27/arch/x86/crypto/ |
| D | crc32c-pcl-intel-asm_64.S | 63 # Define threshold where buffers are considered "small" and routed to more
|
| /linux-4.1.27/Documentation/vm/ |
| D | zswap.txt | 13 is a work in progress and should be considered experimental.
|
| D | active_mm.txt | 62 more. "init_mm" should be considered just a "lazy context when no other
|
| D | page_migration | 78 the new page for each page that is considered for
|
| D | numa_memory_policy.txt | 106 the shared object. However, unlike VMA policies, which can be considered
318 or node lists, if any, for page allocation. This is considered a "hot
440 result is the empty set, the policy is considered invalid and cannot be
|
| /linux-4.1.27/Documentation/frv/ |
| D | configuring.txt | 18 the kernel configuration that need to be considered.
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | boost.txt | 85 This functionality is considered legacy and will be removed in some future
|
| /linux-4.1.27/drivers/staging/unisys/Documentation/ |
| D | proc-entries.txt | 19 guest can be considered running and is shown as running in the s-Par
|
| /linux-4.1.27/Documentation/ABI/ |
| D | README | 77 Notable bits of non-ABI, which should not under any circumstances be considered
|
| /linux-4.1.27/arch/metag/lib/ |
| D | memcpy.S | 99 ! There are 3 mis-alignment cases to be considered. Less than 4 bytes, exactly
|
| /linux-4.1.27/include/uapi/linux/ |
| D | btrfs.h | 228 __u64 considered; /* # of chunks we have considered so far */ member
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 53 of this low power mode would be considered high even though at a cpu level,
|
| /linux-4.1.27/Documentation/thermal/ |
| D | intel_powerclamp.txt | 120 time is considered largely as a non-causal system where its behavior
201 collected during a period without extra interrupts is considered
|
| /linux-4.1.27/arch/powerpc/platforms/ps3/ |
| D | Kconfig | 57 current implementation should be considered experimental.
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | ti-abb-regulator.txt | 42 the regulator. Further, ABB LDOs are considered always-on by
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-piix4 | 53 different 'functions', which can be considered as separate devices). If you
|
| /linux-4.1.27/Documentation/trace/ |
| D | tracepoints.txt | 111 kernel: they are considered as being the same whether they are in the
|
| D | ring-buffer-design.txt | 344 The buffer is considered empty until another full commit finishes.
|
| D | ftrace.txt | 21 Although ftrace is typically considered the function tracer, it
|
| /linux-4.1.27/arch/arm/nwfpe/ |
| D | softfloat-macros | 95 (This routine makes more sense if `a0' and `a1' are considered to form a
220 (This routine makes more sense if `a0', `a1', and `a2' are considered
597 2^31*sqrt(`a'/2^31), where `a' is considered an integer. If bit 0 of `aExp'
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | SoundPro | 52 The IRQ and DMA values can be any that are considered acceptable for a
|
| /linux-4.1.27/kernel/time/ |
| D | Kconfig | 167 system that will be considered to be "small".
|
| /linux-4.1.27/Documentation/gpio/ |
| D | gpio.txt | 13 - The legacy integer-based interface which is considered deprecated (but still
|
| D | driver.txt | 26 Although the integer representation is considered deprecated, it still has many
|
| /linux-4.1.27/Documentation/scsi/ |
| D | aha152x.txt | 133 This is considered to be the default translation.
|
| D | LICENSE.qla4xxx | 127 and can be reasonably considered independent and separate works in
|
| D | scsi_eh.txt | 208 considered to fail always.
|
| D | LICENSE.qla2xxx | 128 and can be reasonably considered independent and separate works in
|
| D | st.txt | 478 The recovered write errors are considered fatal if ST_RECOVERED_WRITE_FATAL
|
| D | ChangeLog.sym53c8xx | 429 Must be considered 100 % trustable, unless I did some mistake
|
| D | ChangeLog.lpfc | 438 that case is considered unpolite, better print messages only for
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 6.Followthrough | 102 If a patch is considered to be a good thing to add to the kernel, and once
201 here first" is not considered to be a compelling technical argument. If
|
| D | 2.Process | 65 considered to be sufficiently stable and the final 2.6.x release is made.
85 break systems which worked in the past are considered to be especially
102 numbering scheme. To be considered for an update release, a patch must (1)
|
| D | 5.Posting | 23 When posting code which is not yet considered ready for inclusion, it is a
81 changes you have made need to be considered in their final form, then
|
| D | 3.Early-stage | 112 data structures in ways which were considered to be unsafe and
|
| D | 1.Intro | 204 lawyer, and nothing in this document can possibly be considered to be
|
| D | 4.Coding | 145 networking in Linux was considered substandard at best, and the Devicescape
|
| /linux-4.1.27/Documentation/laptops/ |
| D | asus-laptop.txt | 93 Note: the display switching code is currently considered EXPERIMENTAL.
|
| D | disk-shock-protection.txt | 133 single project which, although still considered experimental, is fit
|
| D | thinkpad-acpi.txt | 152 Changes to the thinkpad-acpi sysfs interface are only considered
377 Adding other event types for other functionalities shall be considered a
1343 This feature is considered EXPERIMENTAL because it has not been extensively
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | knfsd-stats.txt | 62 an nfsd thread to service it, i.e. no nfsd thread was considered
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | interlaken-lac.txt | 22 considered a different operation mode.
|
| /linux-4.1.27/Documentation/input/ |
| D | multi-touch-protocol.txt | 62 tracking id not previously present is considered new, and a tracking id no
63 longer present is considered removed. Since only changes are propagated,
|
| D | elantech.txt | 169 Probably all the versions with param[0] <= 01 can be considered as
171 4 bytes/firmware 2. Everything >= 02.08.00 can be considered as 6 bytes.
|
| D | joystick-api.txt | 242 such as jscal or kcmjoy. These IOCTLs and data types aren't considered
|
| D | event-codes.txt | 256 considered undefined and the device type should be deduced in the
|
| /linux-4.1.27/Documentation/usb/ |
| D | power-management.txt | 86 communication taking place. (For example, a hub isn't considered idle
88 In addition, a device isn't considered idle so long as a program keeps
365 then the interface is considered to be idle, and the kernel may
697 external hub ports which should be considered 'hotplug'
|
| D | WUSB-Design-overview.txt | 233 are received in some time, the device is considered gone and wiped out
|
| /linux-4.1.27/drivers/cpufreq/ |
| D | Kconfig.x86 | 277 and is thus considered dangerous. Please use the regular ACPI cpufreq
|
| /linux-4.1.27/Documentation/crypto/ |
| D | async-tx-api.txt | 211 considered by the general-purpose allocator even after a call to
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 17 of this GPIO for the device. While a non-existent <name> is considered valid
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-error-recovery.txt | 104 is not implemented, the corresponding feature is considered unsupported.
309 device will be considered "dead" in this case.
|
| /linux-4.1.27/ |
| D | COPYING | 3 services by normal system calls - this is merely considered normal use
132 and can be reasonably considered independent and separate works in
|
| /linux-4.1.27/Documentation/arm64/ |
| D | acpi_object_usage.txt | 106 be considered valid.
322 considered complete without a corresponding _DSD
|
| D | booting.txt | 121 memreserve region in the device tree) will be considered as available to
|
| D | arm-acpi.txt | 279 properties will not be considered complete without their definitions. Once
|
| /linux-4.1.27/tools/usb/usbip/ |
| D | INSTALL | 36 be considered for the next release. If you are using the cache, and at
|
| D | COPYING | 116 and can be reasonably considered independent and separate works in
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.concap | 192 dops pointers. Other concap_proto members should be considered private
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | compress_offload.txt | 205 compressed data interface will be considered as regular ALSA devices;
|
| /linux-4.1.27/tools/perf/Documentation/ |
| D | perf-report.txt | 175 the tree is considered as a new profiled object. +
|
| /linux-4.1.27/Documentation/ia64/ |
| D | fsys.txt | 146 task pointer is not considered sensitive: it's already exposed
|
| /linux-4.1.27/drivers/tty/serial/8250/ |
| D | Kconfig | 256 This is considered unsafe; it is far better to configure the IRQ in
|
| /linux-4.1.27/Documentation/block/ |
| D | cfq-iosched.txt | 53 request, then the seeking cost of two requests is considered equivalent.
|
| D | biodoc.txt | 169 ii. High-mem i/o capabilities are now considered the default
380 The following were some of the goals and expectations considered in the
|
| /linux-4.1.27/tools/perf/ |
| D | design.txt | 267 considered to be a group with only 1 member.)
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | videobuf | 43 functionality is considered to be deprecated for most use, but it still
|
| D | v4l2-controls.txt | 319 and cur.val fields can be considered an alias since these are used so often.
|
| /linux-4.1.27/arch/m68k/fpsp040/ |
| D | setox.S | 101 | This error has to be considered later in Steps 3 and 4.
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1194 to get credit for their work, while not being considered responsible
1292 Disclaimers are considered to be included by reference in this
1402 or the equivalent are not considered part of the section titles.
1498 Translation is considered a kind of modification, so you may
|
| /linux-4.1.27/Documentation/x86/ |
| D | boot.txt | 504 type_of_loader field. The total version number is considered to be
1009 considered an absolutely last resort!
|
| /linux-4.1.27/drivers/staging/rtl8192e/ |
| D | license | 119 reasonably considered independent and separate works in themselves, then
|
| /linux-4.1.27/drivers/staging/rtl8192u/ |
| D | copying | 116 and can be reasonably considered independent and separate works in
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | ide-cd | 310 should be considered obsolete.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | usage-model.txt | 324 considered a device). The children of the /soc node are memory mapped
|
| D | booting-without-of.txt | 175 r1 is not used, but it is considered good practice to use a valid
797 considered a good practice to use a name that is closer to the device
803 restriction on the "name" property; it is simply considered good
|
| /linux-4.1.27/init/ |
| D | Kconfig | 226 exchange information. It is generally considered to be a good thing,
1097 set are considered to be unconstrained and will run with no
1754 the keyring are considered to be trusted. Keys may be added at will
|
| /linux-4.1.27/Documentation/security/ |
| D | credentials.txt | 317 example), it must be considered immutable, barring two exceptions:
|
| D | Smack.txt | 365 Internet Domain IPC: Transmission of a packet is considered a
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 409 rmdir(2). They also are not considered when rmdir(2) on the parent
|
| /linux-4.1.27/net/sched/ |
| D | Kconfig | 22 This code is considered to be experimental.
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 469 files and similar are considered.
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cgroups.txt | 570 callback, @cgrp should be considered dead to the subsystem.
|
| D | memory.txt | 474 kernel pages will still be seen. This is not considered a failure and the
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 308 not considered important at this time as no known operating system does this.
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.lex.c_shipped | 237 /* Whether we're considered to be at the beginning of a line.
|
| /linux-4.1.27/scripts/genksyms/ |
| D | lex.lex.c_shipped | 218 /* Whether we're considered to be at the beginning of a line.
|
| /linux-4.1.27/Documentation/RCU/ |
| D | whatisRCU.txt | 68 during the removal phase need be considered, because any reader starting
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-lexer.lex.c_shipped | 228 /* Whether we're considered to be at the beginning of a line.
|
| /linux-4.1.27/net/netfilter/ |
| D | Kconfig | 96 is considered obsolete in favor of using the conntrack(8)
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 922 considered obsolete in 2.4. Also, the root helper only needs to
3722 field shows whether the page is considered free or not:
|
| /linux-4.1.27/arch/mips/ |
| D | Kconfig | 2662 be considered experimental and only enabled by those working upon
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 773 be considered hung.
|
| /linux-4.1.27/fs/btrfs/ |
| D | volumes.c | 3244 bctl->stat.considered++; in __btrfs_balance()
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | fplsp.S | 6755 # This error has to be considered later in Steps 3 and 4. #
|