| /linux-4.1.27/Documentation/mic/mpssd/ |
| D | mpss | 58 failure
69 failure
100 [ $RETVAL -ne 0 ] && failure || success
138 [ $RETVAL -ne 0 ] && failure || success
176 [ $RETVAL -ne 0 ] && failure || success
|
| /linux-4.1.27/arch/m68k/ifpsp060/ |
| D | os.S | 84 | d1 - 0 = success, !0 = failure
115 | d1 - 0 = success, !0 = failure
147 | d1 - 0 = success, !0 = failure
170 | d1 - 0 = success, !0 = failure
181 | d1 - 0 = success, !0 = failure
206 | d1 - 0 = success, !0 = failure
217 | d1 - 0 = success, !0 = failure
241 | d1 - 0 = success, !0 = failure
263 | d1 - 0 = success, !0 = failure
287 | d1 - 0 = success, !0 = failure
|
| D | iskeleton.S | 195 | d0 = 0 -> success; non-zero -> failure
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | devres.txt | 27 sufficient bugs in ->remove and ->probe failure path. Well, yes,
35 initialization failure don't happen often enough to be noticeable.
36 Init failure path is worse because it's much less travelled while
40 and having half broken failure path implementation in ->probe() which
41 would leak resources or even cause oops when failure occurs. iomap
132 to better maintained higher layer. Also, as init failure path is
142 resources on failure. For example,
163 As resource acquisition failure usually means probe failure, constructs
165 layer) where interface function shouldn't have side effect on failure.
|
| /linux-4.1.27/Documentation/fault-injection/ |
| D | fault-injection.txt | 39 likelihood of failure injection, in percent.
42 Note that one-failure-per-hundred is a very high error rate
68 specifies the verbosity of the messages when failure is
70 log line per failure; '2' will print a call trace too -- useful
162 Upon should_fail() returning true, client code should inject a failure.
253 allocation failure.
264 Same as above except to inject page allocation failure instead of slab
265 allocation failure.
|
| /linux-4.1.27/drivers/dma/ |
| D | ste_dma40.c | 3163 goto failure; in d40_hw_detect_init()
3169 goto failure; in d40_hw_detect_init()
3175 goto failure; in d40_hw_detect_init()
3179 goto failure; in d40_hw_detect_init()
3183 goto failure; in d40_hw_detect_init()
3195 goto failure; in d40_hw_detect_init()
3201 goto failure; in d40_hw_detect_init()
3215 goto failure; in d40_hw_detect_init()
3242 goto failure; in d40_hw_detect_init()
3291 goto failure; in d40_hw_detect_init()
[all …]
|
| /linux-4.1.27/drivers/net/can/sja1000/ |
| D | kvaser_pci.c | 277 goto failure; in kvaser_pci_add_chan()
285 failure: in kvaser_pci_add_chan()
308 goto failure; in kvaser_pci_init_one()
374 failure: in kvaser_pci_init_one()
|
| /linux-4.1.27/drivers/macintosh/ |
| D | windfarm_fcu_controls.c | 172 unsigned char failure; in wf_fcu_fan_get_rpm() local
176 rc = wf_fcu_read_reg(pv, 0xb, &failure, 1); in wf_fcu_fan_get_rpm()
179 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_rpm()
228 unsigned char failure; in wf_fcu_fan_get_pwm() local
233 rc = wf_fcu_read_reg(pv, 0x2b, &failure, 1); in wf_fcu_fan_get_pwm()
236 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_pwm()
|
| D | smu.c | 986 goto failure; in smu_create_sdb_partition()
993 goto failure; in smu_create_sdb_partition()
998 goto failure; in smu_create_sdb_partition()
1002 failure: in smu_create_sdb_partition()
|
| /linux-4.1.27/arch/arm/nwfpe/ |
| D | entry.S | 79 mov r4, lr @ save the failure-return addresses
95 reteq r4 @ no, return failure
|
| /linux-4.1.27/arch/x86/mm/ |
| D | pat_rbtree.c | 137 goto failure; in memtype_rb_check_conflict()
151 goto failure; in memtype_rb_check_conflict()
162 failure: in memtype_rb_check_conflict()
|
| /linux-4.1.27/Documentation/ |
| D | init.txt | 6 Some high-level reasons for failure (listed roughly in order of execution)
39 Please extend this explanation whenever you find new failure causes
44 which can then store the kernel_execve() result value and on failure
|
| D | rpmsg.txt | 76 Returns 0 on success and an appropriate error value on failure.
93 Returns 0 on success and an appropriate error value on failure.
111 Returns 0 on success and an appropriate error value on failure.
123 Returns 0 on success and an appropriate error value on failure.
137 Returns 0 on success and an appropriate error value on failure.
152 Returns 0 on success and an appropriate error value on failure.
203 Returns 0 on success, and an appropriate error value on failure.
|
| D | percpu-rw-semaphore.txt | 19 -ENOMEM on allocation failure.
|
| D | hwspinlock.txt | 53 appropriate error code on failure (e.g. -EINVAL if the hwspinlock
236 Returns 0 on success, or appropriate error code on failure.
300 return 0 on failure and 1 on success. This callback may _not_ sleep.
|
| D | remoteproc.txt | 95 On success, the new rproc is returned, and on failure, NULL.
164 On success, 0 should be returned, and on failure, an appropriate error code.
167 On success, 0 is returned, and on failure, an appropriate error code.
|
| D | CodingStyle | 779 (-Exxx = failure, 0 = success) or a "succeeded" boolean (0 = failure,
793 for success or -EBUSY for failure. In the same way, "PCI device present" is
803 this rule. Generally they indicate failure by returning some out-of-range
805 NULL or the ERR_PTR mechanism to report failure.
|
| D | pnp.txt | 118 - returns zero for success or a negative error number for failure; count
|
| D | DMA-API-HOWTO.txt | 200 This means that in the failure case, you have three options:
635 of sg entries it mapped them to. On failure 0 is returned.
769 failure can be determined by:
859 the failure case.
|
| D | md.txt | 230 by a user-space program. Any device failure or other event that
369 blocked - device has failed, and the failure hasn't been
386 Writing "faulty" simulates a failure on the device.
|
| D | iostats.txt | 131 or failure of the read cannot be attributed to the partition. In other
|
| D | robust-futex-ABI.txt | 31 probably causing deadlock or other such failure of the other threads
|
| D | unshare.txt | 159 On success, zero returned. On failure, -1 is returned and errno is
|
| D | vme_api.txt | 77 failure. For all successful matches, the probe routine of the corresponding
|
| D | DMA-API.txt | 328 mapped them to. On failure 0, is returned.
537 failure.
|
| D | cpu-hotplug.txt | 224 seen any poweroff/reboot failure so far after CPU0 is offline on a few tested
|
| D | ManagementStyle | 123 That may sound like a failure, but it's usually a sign that there was
|
| D | SubmittingPatches | 689 have led to this patch. Including symptoms of the failure which the
692 looking for the applicable patch. If a patch fixes a compile failure,
|
| D | dma-buf-sharing.txt | 61 buffer, so it can be exported. On failure to allocate the dma_buf object,
|
| /linux-4.1.27/tools/testing/selftests/rcutorture/bin/ |
| D | parse-console.sh | 42 print_warning Assertion failure in $file $title
|
| /linux-4.1.27/drivers/net/ethernet/micrel/ |
| D | ks8695net.c | 1386 goto failure; in ks8695_probe()
1396 goto failure; in ks8695_probe()
1404 goto failure; in ks8695_probe()
1417 goto failure; in ks8695_probe()
1427 goto failure; in ks8695_probe()
1469 goto failure; in ks8695_probe()
1528 goto failure; in ks8695_probe()
1535 failure: in ks8695_probe()
|
| /linux-4.1.27/fs/btrfs/ |
| D | sysfs.c | 690 goto failure; in btrfs_sysfs_add_one()
694 goto failure; in btrfs_sysfs_add_one()
700 goto failure; in btrfs_sysfs_add_one()
705 goto failure; in btrfs_sysfs_add_one()
708 failure: in btrfs_sysfs_add_one()
|
| /linux-4.1.27/Documentation/devicetree/bindings/power_supply/ |
| D | sbs_sbs-battery.txt | 9 IO failure.
|
| /linux-4.1.27/net/ipv4/ |
| D | fib_semantics.c | 802 goto failure; in fib_create_info()
807 goto failure; in fib_create_info()
812 goto failure; in fib_create_info()
829 goto failure; in fib_create_info()
867 goto failure; in fib_create_info()
925 goto failure; in fib_create_info()
930 goto failure; in fib_create_info()
981 failure: in fib_create_info()
|
| D | ipmr.c | 431 goto failure; in ipmr_new_tunnel()
438 goto failure; in ipmr_new_tunnel()
444 failure: in ipmr_new_tunnel()
528 goto failure; in ipmr_reg_vif()
537 goto failure; in ipmr_reg_vif()
543 failure: in ipmr_reg_vif()
|
| D | tcp_ipv4.c | 223 goto failure; in tcp_v4_connect()
232 goto failure; in tcp_v4_connect()
250 goto failure; in tcp_v4_connect()
254 failure: in tcp_v4_connect()
|
| /linux-4.1.27/net/sched/ |
| D | act_police.c | 169 goto failure; in tcf_act_police_locate()
175 goto failure; in tcf_act_police_locate()
247 failure: in tcf_act_police_locate()
|
| D | sch_htb.c | 1349 goto failure; in htb_change_class()
1353 goto failure; in htb_change_class()
1357 goto failure; in htb_change_class()
1363 goto failure; in htb_change_class()
1393 goto failure; in htb_change_class()
1398 goto failure; in htb_change_class()
1403 goto failure; in htb_change_class()
1412 goto failure; in htb_change_class()
1523 failure: in htb_change_class()
|
| D | cls_route.c | 140 goto failure; in route4_classify()
156 goto failure; in route4_classify()
195 failure: in route4_classify()
|
| D | sch_cbq.c | 1824 goto failure; in cbq_change_class()
1837 goto failure; in cbq_change_class()
1846 goto failure; in cbq_change_class()
1852 goto failure; in cbq_change_class()
1860 goto failure; in cbq_change_class()
1908 failure: in cbq_change_class()
|
| /linux-4.1.27/arch/ia64/kernel/ |
| D | unaligned.c | 1372 goto failure; in ia64_handle_unaligned()
1427 goto failure; in ia64_handle_unaligned()
1455 goto failure; in ia64_handle_unaligned()
1471 goto failure; in ia64_handle_unaligned()
1501 goto failure; in ia64_handle_unaligned()
1505 goto failure; in ia64_handle_unaligned()
1521 failure: in ia64_handle_unaligned()
|
| /linux-4.1.27/arch/s390/kernel/ |
| D | sclp.S | 108 # R2 = 0 on success, 1 on failure
141 # R2 = 0 on success, non-zero on failure
201 # R2 = 0 on success, 1 on failure
263 # R2 = 0 on success, 1 on failure
|
| /linux-4.1.27/net/decnet/ |
| D | dn_fib.c | 284 goto failure; in dn_fib_create_info()
315 goto failure; in dn_fib_create_info()
365 goto failure; in dn_fib_create_info()
369 goto failure; in dn_fib_create_info()
402 failure: in dn_fib_create_info()
|
| /linux-4.1.27/drivers/target/iscsi/ |
| D | iscsi_target_erl1.c | 1175 goto failure; in iscsit_handle_dataout_timeout()
1182 goto failure; in iscsit_handle_dataout_timeout()
1205 goto failure; in iscsit_handle_dataout_timeout()
1210 goto failure; in iscsit_handle_dataout_timeout()
1218 goto failure; in iscsit_handle_dataout_timeout()
1226 failure: in iscsit_handle_dataout_timeout()
|
| /linux-4.1.27/sound/isa/wavefront/ |
| D | wavefront_synth.c | 1965 goto failure; in wavefront_download_firmware()
1972 goto failure; in wavefront_download_firmware()
1977 goto failure; in wavefront_download_firmware()
1981 goto failure; in wavefront_download_firmware()
1989 goto failure; in wavefront_download_firmware()
1997 goto failure; in wavefront_download_firmware()
2006 failure: in wavefront_download_firmware()
|
| /linux-4.1.27/arch/arm/vfp/ |
| D | entry.S | 45 @ failure to the VFP initialisation code.
|
| /linux-4.1.27/sound/core/oss/ |
| D | pcm_oss.c | 862 goto failure; in snd_pcm_oss_change_params()
885 goto failure; in snd_pcm_oss_change_params()
910 goto failure; in snd_pcm_oss_change_params()
915 goto failure; in snd_pcm_oss_change_params()
951 goto failure; in snd_pcm_oss_change_params()
959 goto failure; in snd_pcm_oss_change_params()
968 goto failure; in snd_pcm_oss_change_params()
976 goto failure; in snd_pcm_oss_change_params()
981 goto failure; in snd_pcm_oss_change_params()
986 goto failure; in snd_pcm_oss_change_params()
[all …]
|
| /linux-4.1.27/scripts/coccinelle/null/ |
| D | eno.cocci | 47 msg = "ERROR: allocation function on line %s returns NULL not ERR_PTR on failure" % (p1[0].line)
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | efivarfs.txt | 22 but it does prevent this kind of failure from being accomplished
|
| D | path-lookup.txt | 195 failure.
315 a better errno) to signal an rcu-walk failure.
342 drop rcu that fail due to d_seq failure and requiring the entire path lookup
368 dentry not existing (which can be common) is not necessarily a failure of
|
| D | ceph.txt | 11 * High availability and reliability. No single point of failure.
|
| D | vfs.txt | 159 superblock must be locked. On failure it should return ERR_PTR(error).
676 Returns 0 on success; < 0 on failure (which is the error code), in
687 Returns < 0 on failure, otherwise the number of bytes (<= 'copied')
721 indicate failure with a 0 return value.
751 that is signalling imminent failure) it will pass a new page
775 is ok for this address space. Used for memory failure handling.
1031 the case of failure. The vfsmount should be returned with 2 refs on
|
| D | xfs-self-describing-metadata.txt | 124 events that lead to the eventual failure, and even whether there are corruptions
|
| D | Locking | 282 Note, failure to run either redirty_page_for_writepage() or the combination of
|
| D | coda.txt | 692 indicates success or failure.
855 relevant. It indicates success or the type of failure.
|
| D | xfs-delayed-logging-design.txt | 301 failure and an inconsistent filesystem and hence we must enforce the maximum
|
| /linux-4.1.27/arch/x86/kernel/acpi/ |
| D | wakeup_32.S | 79 # In case of S3 failure, we'll emerge here. Jump
|
| /linux-4.1.27/fs/reiserfs/ |
| D | inode.c | 734 goto failure; in reiserfs_get_block()
743 goto failure; in reiserfs_get_block()
775 goto failure; in reiserfs_get_block()
787 goto failure; in reiserfs_get_block()
884 goto failure; in reiserfs_get_block()
924 goto failure; in reiserfs_get_block()
951 goto failure; in reiserfs_get_block()
962 goto failure; in reiserfs_get_block()
1086 goto failure; in reiserfs_get_block()
1114 goto failure; in reiserfs_get_block()
[all …]
|
| /linux-4.1.27/Documentation/vm/ |
| D | hwpoison.txt | 13 * failure.
36 The code consists of a the high level handler in mm/memory-failure.c,
51 There are two (actually three) modi memory failure recovery can be in:
|
| D | zsmalloc.txt | 21 uncompressed form). For allocation requests larger than this size, failure
|
| D | numa | 139 itself on allocation failure. The kernel profiling subsystem is an example of
|
| D | transhuge.txt | 45 the same vma without any failure or significant delay and without
150 allocation failure to throttle the next allocation attempt.
|
| D | cleancache.txt | 42 a negative return value indicates failure. A "put_page" will copy a
|
| D | frontswap.txt | 38 If a store returns failure, transcendent memory has rejected the data, and the
|
| D | hugetlbpage.txt | 99 The success or failure of huge page allocation depends on the amount of
|
| D | unevictable-lru.txt | 448 page on failure - will be freed when the reference count held by the migration
|
| /linux-4.1.27/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 33 This routine returns zero on success and a negative errno code for failure.
125 parameter. It returns zero on success or a negative errno code for failure.
128 parameter. It returns zero on success or a negative errno code for failure.
140 parameter. It returns zero on success or a negative errno code for failure.
226 This routine returns zero on success and a negative errno code for failure.
|
| /linux-4.1.27/Documentation/power/ |
| D | basic-pm-debugging.txt | 143 A failure of any of the "platform", "processors" or "core" tests may cause your
144 system to hang or become unstable, so please beware. Such a failure usually
175 information about the reasons of the suspend (resume) failure. Alternatively,
227 the failure number. Others are the failure number of different steps of suspend
|
| D | s2ram.txt | 83 quickly after the resume failure. The trace option does not use the seconds
|
| D | freezing-of-tasks.txt | 191 at this point. So, seemingly, the failure is due to the freezing of tasks.
218 leading to freezing failure.
|
| D | suspend-and-cpuhotplug.txt | 274 As a result of this task freezing failure, the suspend operation gets
|
| D | runtime_pm.txt | 312 error code on failure, where -EINPROGRESS means that ->runtime_idle() is
319 error code on failure, where -EAGAIN or -EBUSY means it is safe to attempt
332 error code on failure, where -EAGAIN means it may be safe to attempt to
|
| D | swsusp.txt | 120 seconds to failure. What do you do? Suspend to disk.
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-fcoe | 51 lesb/link_fail: Link Error Status Block (LESB) link failure count.
54 failure count.
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | imx28-duckbill.dts | 116 failure {
|
| /linux-4.1.27/drivers/md/ |
| D | Kconfig | 86 of each other. In the event of a mirror failure, the RAID driver
90 of a single drive, and the set protects against a failure of (N - 1)
132 the capacity of C * (N - 1) MB, and protects against a failure
141 against a failure of any two drives. For a given sector
355 the capacity of C * (N - 1) MB, and protects against a failure
364 against a failure of any two drives. For a given sector
|
| /linux-4.1.27/fs/minix/ |
| D | itree_common.c | 47 goto failure; in get_branch()
63 failure: in get_branch()
|
| /linux-4.1.27/net/dccp/ |
| D | ipv4.c | 108 goto failure; in dccp_v4_connect()
115 goto failure; in dccp_v4_connect()
129 goto failure; in dccp_v4_connect()
132 failure: in dccp_v4_connect()
|
| D | ipv6.c | 887 goto failure; in dccp_v6_connect()
910 goto failure; in dccp_v6_connect()
948 failure: in dccp_v6_connect()
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | hugetlb.txt | 33 hugetlb.<hugepagesize>.failcnt # show the number of allocation failure due to HugeTLB limit
|
| D | memory.txt | 474 kernel pages will still be seen. This is not considered a failure and the
552 This failcnt(== failure count) shows the number of times that a usage counter
|
| D | cgroups.txt | 382 Note that specifying 'release_agent' more than once will return failure.
|
| /linux-4.1.27/drivers/net/ethernet/xircom/ |
| D | xirc2ps_cs.c | 706 goto failure; in xirc2ps_config()
729 goto failure; in xirc2ps_config()
735 goto failure; in xirc2ps_config()
761 goto failure; in xirc2ps_config()
923 failure: in xirc2ps_config()
|
| /linux-4.1.27/drivers/infiniband/ulp/iser/ |
| D | iscsi_iser.c | 813 goto failure; in iscsi_iser_ep_connect()
822 goto failure; in iscsi_iser_ep_connect()
825 failure: in iscsi_iser_ep_connect()
|
| D | iser_verbs.c | 799 goto failure; in iser_route_handler()
816 goto failure; in iser_route_handler()
820 failure: in iser_route_handler()
|
| /linux-4.1.27/fs/squashfs/ |
| D | file.c | 193 goto failure; in read_indexes()
206 failure: in read_indexes()
|
| /linux-4.1.27/fs/jffs2/ |
| D | TODO | 37 case of failure? scan() does not clean everything. Fix.
|
| /linux-4.1.27/mm/ |
| D | Makefile | 66 obj-$(CONFIG_MEMORY_FAILURE) += memory-failure.o
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 31 - Check against memory allocation failure for SCRIPTZ and add the
48 - Cleanup a bit the PPR failure recovery code.
|
| D | scsi_eh.txt | 216 cannot recover some of failed scmds. Also, note that failure of the
217 highest-severity action means EH failure and results in offlining of
240 either retry or error-finish (notify upper layer of failure) recovered
274 layer of failure.
422 layer of failure of the scmds.
|
| D | ChangeLog.ips | 59 4.20.13 - Fix some failure cases / reset code
|
| D | scsi_mid_low_api.txt | 422 * Returns 0 on success, negative errno of failure (e.g. -ENOMEM)
463 * Returns pointer to partition table, or NULL for failure
498 * Returns pointer to new Scsi_Host instance or NULL on failure
558 * Returns 0 on success, -1 on failure
576 * Returns pointer to new Scsi_Host instance or NULL on failure
614 * Returns value: 0 on success, 1 on failure (e.g. LLD busy ??)
1011 * If there's a failure, return either:
|
| D | scsi_fc_transport.txt | 332 - The link may be down. It is not a failure if it is. It simply
341 failure cases for quicker resolution.
|
| D | ChangeLog.ncr53c8xx | 384 interrupt code in case of negotiation failure.
|
| D | ChangeLog.megaraid | 6 1. Changes in Initialization to fix kdump failure.
|
| D | ChangeLog.megaraid_sas | 152 1. Fix some failure gotos from megasas_probe_one(), etc.
|
| D | ChangeLog.lpfc | 522 * Zero out seg_cnt in prep_io failure path to prevent double sg
967 * Removed LPFC_DEV_RPTLUN node failure bit because we don't issue
1390 * Detect failure return from pci_map_sg call in lpfc_os_prep_io
|
| /linux-4.1.27/drivers/net/wireless/libertas_tf/ |
| D | if_usb.c | 685 u8 failure; in if_usb_receive() local
689 failure = (tmp & 0xff00) >> 8; in if_usb_receive()
690 lbtf_send_tx_feedback(priv, retrycnt, failure); in if_usb_receive()
|
| /linux-4.1.27/tools/testing/fault-injection/ |
| D | failcmd.sh | 25 likelihood of failure injection, in percent.
|
| /linux-4.1.27/drivers/net/wireless/zd1211rw/ |
| D | zd_mac.h | 154 u8 failure; member
|
| D | zd_mac.c | 456 success = !tx_status->failure; in zd_mac_tx_status()
507 int success = !tx_status->failure; in zd_mac_tx_failed()
527 if (tx_status->failure && mac->ack_pending && in zd_mac_tx_failed()
|
| /linux-4.1.27/fs/ext4/ |
| D | indirect.c | 160 goto failure; in ext4_get_branch()
166 goto failure; in ext4_get_branch()
171 goto failure; in ext4_get_branch()
182 failure: in ext4_get_branch()
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | dm-uevent.txt | 67 1.) Path failure.
|
| D | era.txt | 100 crash such as power failure.
|
| D | persistent-data.txt | 49 On power failure your metadata will be as it was when last committed.
|
| D | dm-io.txt | 65 indicate success or failure on each individual region.
|
| D | log-writes.txt | 35 cases where a power failure at a particular point in time would create an
|
| D | dm-raid.txt | 58 resyncing after a failure is likely to take longer.
|
| /linux-4.1.27/fs/sysv/ |
| D | itree.c | 105 goto failure; in get_branch()
118 failure: in get_branch()
|
| /linux-4.1.27/arch/frv/mm/ |
| D | tlb-miss.S | 43 # handle a lookup failure of one sort or another in a kernel TLB handler
88 # handle a lookup failure of one sort or another in a user TLB handler
|
| /linux-4.1.27/Documentation/networking/ |
| D | cxacru.txt | 91 "poll" (used to resume status polling if it was disabled due to failure)
|
| D | xfrm_sync.txt | 137 or failure.
|
| D | lapb-module.txt | 72 is the maximum number of tries on the link before it is declared a failure.
|
| D | bonding.txt | 217 802.3ad aggregations when partial failure of the active aggregator
327 the active slave failure, it doesn't really guarantee that the
382 a slave after a link failure has been detected. This option
709 when failure of the active slave or recovery of the primary slave
725 failure or 2
1953 use_carrier=0 to see if that improves the failure detection time. If
2035 the active slave changes (e.g., due to a link failure), the
2120 thus detecting that failure without switch support.
2124 end connectivity failures (which may be caused by the failure of any
2422 failure). If you find this to be a problem, specify an appropriate
|
| D | arcnet.txt | 31 If you don't e-mail me about your success/failure soon, I may be forced to
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | cafe_ccic | 25 perhaps decreases the chances of an allocation failure later on.
|
| D | videobuf | 176 are void functions which, evidently, are immune to failure.
|
| /linux-4.1.27/arch/powerpc/kernel/ |
| D | iommu.c | 486 goto failure; in ppc_iommu_map_sg()
502 goto failure; in ppc_iommu_map_sg()
556 failure: in ppc_iommu_map_sg()
|
| /linux-4.1.27/include/uapi/linux/ |
| D | audit.h | 409 __u32 failure; /* Failure-to-log action */ member
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-error-recovery.txt | 223 Same as above. Total failure, no recovery even after
303 A driver can still return a critical failure for this function if
308 will typically report a "permanent failure" in such a case. The
355 A "permanent failure" has occurred, and the platform cannot recover
366 permanent failure in some way. If the device is hotplug-capable,
|
| D | pcieaer-howto.txt | 96 failure.
|
| /linux-4.1.27/drivers/net/wireless/libertas/ |
| D | README | 142 Value field specifies the consecutive failure count threshold which
144 generated, the consecutive failure count is reset to 0.
|
| /linux-4.1.27/drivers/staging/media/omap4iss/ |
| D | iss.c | 583 int failure = 0; in iss_pipeline_disable() local
611 failure = -ETIMEDOUT; in iss_pipeline_disable()
615 return failure; in iss_pipeline_disable()
|
| /linux-4.1.27/Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 26 * Compromise by not reporting a failure to get this
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | g762 | 35 fan1_fault: reports fan failure, i.e. no transition on fan gear pin for
|
| D | hwmon-kernel-api.txt | 43 or PTR_ERR for failure. If this registration function is used, hardware
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 107 Fix premature write failure on congested networks (we would give up
137 cached files. Fix setxattr failure to certain Samba versions. Fix mount
155 connect fails (e.g. due to signing negotiation failure) fix
470 network failure) fix tcp session reconnect code so we do not try first
581 to the kernel log). Fix intermittent failure in connectathon
654 Fix unload_nls oops in a mount failure path. Serialize writes to same socket
671 Fix unsafe global variable usage and password hash failure on gcc 3.3.1
673 failure. Fix invalid dentry - race in mkdir when directory gets created
684 Fix errors in reconnecting after TCP session failure. Fix module unloading
728 during auto reconnection to server after server recovered from failure.
[all …]
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.hysdn | 106 2 -> card is in an error state due to a previous boot failure
131 1006 Second boot stage failure
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | transactional_memory.txt | 60 abort handler can check the cause of the failure, and retry.
195 presented). The transaction cannot then be continued and will take the failure
|
| D | eeh-pci-error-recovery.txt | 36 EEH was originally designed to guard against hardware failure, such
154 allow any interested parties to find out about the failure. Device
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | hdspm.txt | 206 has a failure, there is a takeover to the working one, with no
207 sample failure. Its only useful if you use the second as a
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | README.DAC960 | 86 disks the device names will not change in the event of a disk drive failure.
451 1:1 is now disconnected, simulating a drive failure. The failure is noted by
466 from /proc/rd also reflects the drive failure. The status message in
623 1:2 is now disconnected, simulating a drive failure. The failure is noted by
642 reflects the drive failure and automatic rebuild. The status message in
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | dmatest.txt | 37 emitted. After that only test failure messages are reported until the test
|
| /linux-4.1.27/arch/sparc/kernel/ |
| D | etrap_32.S | 273 bne trap_setup_user_stack_is_bolixed ! failure
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | core.txt | 65 hardware failure.
|
| /linux-4.1.27/fs/ext3/ |
| D | Kconfig | 40 power failure, which can be a security issue. However,
|
| D | inode.c | 425 goto failure; in ext3_get_branch()
440 failure: in ext3_get_branch()
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 405 failue||failure
406 failuer||failure
408 faliure||failure
|
| /linux-4.1.27/Documentation/frv/ |
| D | atomic-ops.txt | 101 It simultaneously records the success or failure of the store in ICC3.Z.
|
| /linux-4.1.27/Documentation/devicetree/bindings/c6x/ |
| D | dscr.txt | 32 failure.
|
| /linux-4.1.27/drivers/net/ethernet/ibm/ |
| D | ibmveth.c | 244 goto failure; in ibmveth_replenish_buffer_pool()
266 goto failure; in ibmveth_replenish_buffer_pool()
277 failure: in ibmveth_replenish_buffer_pool()
|
| /linux-4.1.27/net/core/ |
| D | sock.c | 1816 goto failure; in sock_alloc_send_pskb()
1820 goto failure; in sock_alloc_send_pskb()
1829 goto failure; in sock_alloc_send_pskb()
1842 failure: in sock_alloc_send_pskb()
|
| D | skbuff.c | 4421 goto failure; in alloc_skb_with_frags()
4431 failure: in alloc_skb_with_frags()
|
| /linux-4.1.27/arch/mips/kernel/ |
| D | r4k_fpu.S | 281 fault: li v0, -EFAULT # failure
|
| /linux-4.1.27/Documentation/usb/ |
| D | error-codes.txt | 108 error, a failure to respond (often caused by
|
| D | power-management.txt | 406 idle. This is perfectly normal. If the reason for failure was that
411 Autoresume attempts also can fail, although failure would mean that
|
| /linux-4.1.27/drivers/usb/gadget/ |
| D | Kconfig | 57 either create new failure modes or remove the one you're
71 either create new failure modes or remove the one you're
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 6.Followthrough | 15 standards. A failure to participate in this process is quite likely to
158 having a patch pulled as the result of a failure to fix a regression could
|
| D | 1.Intro | 253 the licensing of the kernel is doomed to almost certain failure. There are
|
| D | 4.Coding | 270 fact of the matter, though, is that the resulting failure recovery paths
|
| /linux-4.1.27/drivers/s390/char/ |
| D | raw3270.c | 1174 goto failure; in raw3270_set_online()
1182 failure: in raw3270_set_online()
|
| /linux-4.1.27/Documentation/hid/ |
| D | hid-transport.txt | 68 device failures. Once transport drivers detect unplug or failure events, they
83 retransmission on failure, etc. in a blocking manner. If such functionality is
|
| /linux-4.1.27/Documentation/arm/nwfpe/ |
| D | README.FPE | 144 is caused by a failure to alias fp_current to the kernel variable
|
| /linux-4.1.27/Documentation/laptops/ |
| D | asus-laptop.txt | 243 I appreciate any success or failure
|
| D | thinkpad-acpi.txt | 51 site, http://ibm-acpi.sf.net/. I appreciate any success or failure
|
| /linux-4.1.27/drivers/media/platform/omap3isp/ |
| D | isp.c | 978 int failure = 0; in isp_pipeline_disable() local
1034 failure = -ETIMEDOUT; in isp_pipeline_disable()
1038 return failure; in isp_pipeline_disable()
|
| /linux-4.1.27/net/ipv6/ |
| D | tcp_ipv6.c | 222 goto failure; in tcp_v6_connect()
248 goto failure; in tcp_v6_connect()
300 failure: in tcp_v6_connect()
|
| D | ip6mr.c | 763 goto failure; in ip6mr_reg_vif()
768 failure: in ip6mr_reg_vif()
|
| /linux-4.1.27/Documentation/misc-devices/mei/ |
| D | mei.txt | 186 IT knows when a platform crashes even when there is a hard failure on the host.
|
| /linux-4.1.27/Documentation/fb/ |
| D | sstfb.txt | 16 Please read the Bug section, and report any success or failure to me
|
| /linux-4.1.27/Documentation/power/regulator/ |
| D | consumer.txt | 170 consumers under regulator stress or failure conditions.
|
| /linux-4.1.27/fs/ext2/ |
| D | inode.c | 248 goto failure; in ext2_get_branch()
264 failure: in ext2_get_branch()
|
| /linux-4.1.27/net/netlink/ |
| D | af_netlink.c | 1964 int failure; member
1990 if (p->failure) { in do_one_broadcast()
2011 p->failure = 1; in do_one_broadcast()
2047 info.failure = 0; in netlink_broadcast_filtered()
|
| /linux-4.1.27/drivers/net/wireless/mwifiex/ |
| D | README | 152 num_cmd_assoc_fail = <number of associate commands with failure return>
|
| /linux-4.1.27/ |
| D | REPORTING-BUGS | 88 If the failure includes an "OOPS:", take a picture of the screen, capture
|
| /linux-4.1.27/kernel/ |
| D | audit.c | 832 s.failure = audit_failure; in audit_receive_msg()
854 err = audit_set_failure(s.failure); in audit_receive_msg()
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 391 still having a valid copy on disk) the kernel will handle the failure
416 Enable memory failure recovery (when supported by the platform)
420 0: Always panic on a memory failure.
|
| /linux-4.1.27/fs/affs/ |
| D | Changes | 12 apparently not causing the failure, as directory
|
| /linux-4.1.27/Documentation/i2c/ |
| D | dev-interface | 160 All these transactions return -1 on failure; you can read errno to see
|
| D | writing-clients | 387 All these transactions return a negative errno value on failure. The 'write'
|
| /linux-4.1.27/tools/perf/util/ |
| D | machine.c | 759 goto failure; in machines__create_guest_kernel_maps()
763 failure: in machines__create_guest_kernel_maps()
|
| /linux-4.1.27/Documentation/input/ |
| D | input-programming.txt | 167 in case of failure. The close() callback (which is void) must always succeed.
|
| /linux-4.1.27/arch/powerpc/ |
| D | Kconfig.debug | 13 Only enable this if you are hitting a build failure in the
|
| /linux-4.1.27/Documentation/x86/ |
| D | exception-tables.txt | 284 successful, -EFAULT on failure. Our original code did not test this
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | object.txt | 180 failure for whatever reason, and should call fscache_obtained_object() to
|
| D | fscache.txt | 286 rej=N Number of async ops rejected due to object lookup/create failure
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | boot-options.txt | 57 threshold to 1. Enabling this may make memory predictive failure
|
| /linux-4.1.27/drivers/net/wireless/ |
| D | mac80211_hwsim.c | 3122 goto failure; in hwsim_init_netlink()
3126 goto failure; in hwsim_init_netlink()
3130 failure: in hwsim_init_netlink()
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | at91-clock.txt | 154 18 (AT91_PMC_CFDEV) -> clock failure detected
|
| /linux-4.1.27/Documentation/block/ |
| D | data-integrity.txt | 29 of failure.
|
| /linux-4.1.27/Documentation/locking/ |
| D | lockdep-design.txt | 235 normally results from lock-class leakage or failure to properly
|
| /linux-4.1.27/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 93 * Have simple testcases for every input validation failure case in your ioctl.
|
| /linux-4.1.27/Documentation/RCU/ |
| D | stallwarn.txt | 229 o A hardware failure. This is quite unlikely, but has occurred
|
| D | trace.txt | 253 failure to begin an expedited grace period.
|
| /linux-4.1.27/Documentation/video4linux/cx2341x/ |
| D | fw-encoder-api.txt | 698 8=enable scene change detection (seems to be a failure)
|
| /linux-4.1.27/Documentation/nfc/ |
| D | nfc-hci.txt | 138 success, negative for failure).
|
| /linux-4.1.27/Documentation/serial/ |
| D | driver | 289 returns, and it should return -EBUSY on failure.
|
| /linux-4.1.27/drivers/media/radio/ |
| D | Kconfig | 362 in case of automatic probing failure, ie. as a fallback.
|
| /linux-4.1.27/firmware/keyspan_pda/ |
| D | keyspan_pda.S | 679 setb c ; c=1: failure
|
| D | xircom_pgs.S | 717 setb c ; c=1: failure
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 375 this is a void function and cannot return failure. The subsystem is
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 767 failure. The structure $<device>_info$ should have a pointer to the
786 success, and non-zero upon failure.
|
| /linux-4.1.27/scripts/genksyms/ |
| D | parse.tab.c_shipped | 2264 /* Return failure if at end of input. */
|
| /linux-4.1.27/drivers/block/ |
| D | DAC960.c | 6139 goto failure; in DAC960_V1_ExecuteUserCommand()
6158 failure: in DAC960_V1_ExecuteUserCommand()
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 2153 /* Return failure if at end of input. */
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 2166 /* Return failure if at end of input. */
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 1824 Returns: 0 on success, negative value on failure
2076 Returns: 0 on success, negative value on failure
|
| /linux-4.1.27/Documentation/security/ |
| D | keys.txt | 989 is returned upon failure (use IS_ERR/PTR_ERR to determine). If successful,
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 1618 recovery of all the possible two disk failure scenarios for a
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1215 bool "ARM errata: TLBI/DSB failure on Cortex-A15"
|