Home
last modified time | relevance | path

Searched refs:safe (Results 1 – 200 of 301) sorted by relevance

12

/linux-4.1.27/arch/arm/common/
Ddmabounce.c57 void *safe; member
138 buf->safe = dma_pool_alloc(pool->pool, GFP_ATOMIC, in alloc_safe_buffer()
141 buf->safe = dma_alloc_coherent(dev, size, &buf->safe_dma_addr, in alloc_safe_buffer()
145 if (buf->safe == NULL) { in alloc_safe_buffer()
200 dma_pool_free(buf->pool->pool, buf->safe, buf->safe_dma_addr); in free_safe_buffer()
202 dma_free_coherent(device_info->dev, buf->size, buf->safe, in free_safe_buffer()
263 buf->safe, buf->safe_dma_addr); in map_single()
267 __func__, ptr, buf->safe, size); in map_single()
268 memcpy(buf->safe, ptr, size); in map_single()
282 buf->safe, buf->safe_dma_addr); in unmap_single()
[all …]
/linux-4.1.27/drivers/usb/serial/
Dsafe_serial.c84 static bool safe = 1; variable
94 module_param(safe, bool, 0);
95 MODULE_PARM_DESC(safe, "Turn Safe Encapsulation On/Off");
205 if (!safe) in safe_process_read_urb()
236 trailer_len = safe ? 2 : 0; in safe_prepare_write_buffer()
240 if (!safe) in safe_prepare_write_buffer()
/linux-4.1.27/arch/um/
DKconfig.char36 It is safe to say 'Y' here.
46 It is safe to say 'Y' here.
55 It is safe to say 'Y' here.
63 It is safe to say 'Y' here.
77 It is safe to leave this unchanged.
87 It is safe to leave this unchanged, although you may wish to change
99 It is safe to leave this unchanged, although you may wish to change
109 It is safe to say 'Y' here.
DKconfig.um60 it is safe to say 'N' here.
77 It is safe to say 'Y' here.
/linux-4.1.27/fs/ntfs/
DKconfig8 safe, write support available. For write support you must also
27 Linux on your computer it is safe to say N.
55 This enables the partial, but safe, write support in the NTFS driver.
65 damaged someones data so we assume it is perfectly safe to use.
67 Note: While write support is safe in this version (a rewrite from
70 is not safe.
78 It is perfectly safe to say N here.
/linux-4.1.27/Documentation/scsi/
Ddc395x.txt7 be safe to use. Testing with hard disks has not been done to any
28 - safe
31 If safe is set to 1 then the adapter will use conservative
32 ("safe") default settings. This sets:
88 dc395x. (eg "dc395x.safe=1")
Dncr53c8xx.txt310 checking. These features must be enabled in order to ensure safe data
855 Boot fail safe
856 safe:y load the following assumed fail safe initial setup
888 For an installation diskette or a safe but not fast system,
891 ncr53c8xx=safe:y,mpar:y,disc:y
892 ncr53c8xx=safe:y,disc:y
893 ncr53c8xx=safe:y,mpar:y
894 ncr53c8xx=safe:y
1253 with this safe configuration but performances will not be optimal.
D53c700.txt117 to the board designer. Usually it is safe to ignore this setting.
Dsym53c8xx_2.txt281 checking. These features must be enabled in order to ensure safe
524 to any device on the bus. The default is 3 seconds and safe mode will
594 with this safe configuration but performances will not be optimal.
/linux-4.1.27/drivers/ide/
Dtx4938ide.c62 u8 safe = drive->pio_mode - XFER_PIO_0; in tx4938ide_set_pio_mode() local
67 safe = min_t(u8, safe, pair->pio_mode - XFER_PIO_0); in tx4938ide_set_pio_mode()
68 tx4938ide_tune_ebusc(pdata->ebus_ch, pdata->gbus_clock, safe); in tx4938ide_set_pio_mode()
Dtx4939ide.c112 u8 safe = pio; in tx4939ide_set_pio_mode() local
117 safe = min_t(u8, safe, pair->pio_mode - XFER_PIO_0); in tx4939ide_set_pio_mode()
123 val = ((safe << 8) | (pio << 4)) << (is_slave ? 16 : 0); in tx4939ide_set_pio_mode()
DKconfig426 It is safe to say Y to this question.
436 It is safe to say Y to this question.
446 It is safe to say Y to this question.
/linux-4.1.27/drivers/parport/
DKconfig31 and it is safe to compile all the corresponding drivers into the
83 is safe to say N.
99 called parport_ip32. If in doubt, saying N is the safe plan.
108 called parport_amiga. If in doubt, saying N is the safe plan.
117 parport_mfc3. If in doubt, saying N is the safe plan.
126 called parport_atari. If in doubt, saying N is the safe plan.
160 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
/linux-4.1.27/drivers/gpu/drm/ttm/
Dttm_execbuf_util.c123 struct ttm_validate_buffer *safe = entry; in ttm_eu_reserve_buffers() local
125 list_del(&safe->head); in ttm_eu_reserve_buffers()
126 list_add(&safe->head, dups); in ttm_eu_reserve_buffers()
/linux-4.1.27/net/ax25/
DTODO2 listen_lock have to be bh-safe?
4 Do the netrom and rose locks have to be bh-safe?
/linux-4.1.27/drivers/gpu/drm/omapdrm/
Dtcm.h323 #define tcm_for_each_slice(var, area, safe) \ argument
324 for (safe = area, \
325 tcm_slice(&safe, &var); \
326 var.tcm; tcm_slice(&safe, &var))
/linux-4.1.27/drivers/usb/wusbcore/
DKconfig15 To compile this support select Y (built in). It is safe to
29 It is safe to select even if you don't have a compatible
/linux-4.1.27/fs/dlm/
Drequestqueue.c158 struct rq_entry *e, *safe; in dlm_purge_requestqueue() local
161 list_for_each_entry_safe(e, safe, &ls->ls_requestqueue, list) { in dlm_purge_requestqueue()
Dast.c295 struct dlm_lkb *lkb, *safe; in dlm_callback_resume() local
304 list_for_each_entry_safe(lkb, safe, &ls->ls_cb_delay, lkb_cb_list) { in dlm_callback_resume()
Dlock.c2757 struct dlm_lkb *lkb, *safe; in process_lookup_list() local
2759 list_for_each_entry_safe(lkb, safe, &r->res_lookup, lkb_rsb_lookup) { in process_lookup_list()
5118 struct dlm_lkb *lkb, *safe; in dlm_recover_waiters_pre() local
5131 list_for_each_entry_safe(lkb, safe, &ls->ls_waiters, lkb_wait_reply) { in dlm_recover_waiters_pre()
5364 struct dlm_lkb *lkb, *safe; in purge_mstcpy_list() local
5366 list_for_each_entry_safe(lkb, safe, list, lkb_statequeue) { in purge_mstcpy_list()
5397 struct dlm_lkb *lkb, *safe; in purge_dead_list() local
5399 list_for_each_entry_safe(lkb, safe, list, lkb_statequeue) { in purge_dead_list()
6173 struct dlm_lkb *lkb, *safe; in dlm_clear_proc_locks() local
6197 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
[all …]
Dmember.c531 struct dlm_member *memb, *safe; in dlm_recover_members() local
545 list_for_each_entry_safe(memb, safe, &ls->ls_nodes, list) { in dlm_recover_members()
Drecover.c923 struct dlm_rsb *r, *safe; in dlm_release_root_list() local
926 list_for_each_entry_safe(r, safe, &ls->ls_root_list, res_root_list) { in dlm_release_root_list()
Dlowcomms.c1627 struct writequeue_entry *e, *safe; in clean_one_writequeue() local
1630 list_for_each_entry_safe(e, safe, &con->writequeue, list) { in clean_one_writequeue()
1820 struct dlm_node_addr *na, *safe; in dlm_lowcomms_exit() local
1823 list_for_each_entry_safe(na, safe, &dlm_node_addrs, list) { in dlm_lowcomms_exit()
/linux-4.1.27/drivers/uwb/
DKconfig40 is safe to select any even if you do not have the hardware.
56 is safe to select any even if you do not have the hardware.
68 is safe to select any even if you do not have the hardware.
Drsv.c361 rsv->mas.safe += mv->companion_mas.safe; in uwb_rsv_set_state()
368 rsv->mas.safe = mv->final_mas.safe; in uwb_rsv_set_state()
Dallocator.c376 result->safe = ai->safe_allocated_mases; in uwb_rsv_find_best_allocation()
/linux-4.1.27/arch/cris/arch-v32/mach-fs/
DKconfig96 stuff. If you don't know what to use, it is always safe to put all
118 stuff. If you don't know what to use, it is always safe to put all
140 stuff. If you don't know what to use, it is always safe to put all
162 stuff. If you don't know what to use, it is always safe to put all
184 stuff. If you don't know what to use, it is always safe to put all
203 what to use, it is always safe to put all as inputs, although
/linux-4.1.27/Documentation/locking/
Dlockdep-design.txt72 <hardirq-safe> and <hardirq-unsafe>
73 <softirq-safe> and <softirq-unsafe>
97 <hardirq-safe> -> <hardirq-unsafe>
98 <softirq-safe> -> <softirq-unsafe>
100 The first rule comes from the fact the a hardirq-safe lock could be
102 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
113 - if a new hardirq-safe lock is discovered, we check whether it
116 - if a new softirq-safe lock is discovered, we check whether it took
120 hardirq-safe lock took it in the past.
123 softirq-safe lock took it in the past.
Dspinlocks.txt13 The above is always safe. It will disable interrupts _locally_, but the
38 NOTE! The spin-lock is safe only when you _also_ use the lock itself
92 are the most safe ones, and the ones that work under all circumstances,
93 but partly _because_ they are safe they are also fairly slow. They are slower
137 But when you do the write-lock, you have to use the irq-safe version.
142 wake up. So read-locks are safe (which is good: they are very common
/linux-4.1.27/arch/powerpc/platforms/52xx/
DKconfig19 gpt nodes, then it is safe to use such gpt to reset the board,
56 It is safe to say 'Y' here
/linux-4.1.27/arch/cris/arch-v32/mach-a3/
DKconfig58 stuff. If you don't know what to use, it is always safe to put all
78 stuff. If you don't know what to use, it is always safe to put all
98 stuff. If you don't know what to use, it is always safe to put all
/linux-4.1.27/net/batman-adv/
Dtranslation-table.c348 struct batadv_tt_change_node *tt_change_node, *entry, *safe; in batadv_tt_local_event() local
368 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_local_event()
835 struct batadv_tt_change_node *entry, *safe; in batadv_tt_tvlv_container_update() local
864 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_tvlv_container_update()
1197 struct batadv_tt_change_node *entry, *safe; in batadv_tt_changes_list_free() local
1201 list_for_each_entry_safe(entry, safe, &bat_priv->tt.changes_list, in batadv_tt_changes_list_free()
1653 struct hlist_node *safe; in batadv_tt_global_del_orig_list() local
1658 hlist_for_each_entry_safe(orig_entry, safe, head, list) in batadv_tt_global_del_orig_list()
1680 struct hlist_node *safe; in batadv_tt_global_del_orig_node() local
1686 hlist_for_each_entry_safe(orig_entry, safe, head, list) { in batadv_tt_global_del_orig_node()
[all …]
/linux-4.1.27/drivers/remoteproc/
DKconfig31 It's safe to say n here if you're not interested in multimedia
64 It's safe to say n here if you're not interested in multimedia
/linux-4.1.27/drivers/of/
DKconfig19 If unsure, say N here, but this option is safe to enable.
34 # Hardly any platforms need this. It is safe to select, but only do so if you
/linux-4.1.27/drivers/clocksource/
Dem_sti.c288 int safe; in em_sti_clock_event_next() local
291 safe = em_sti_count(p) < (next - 1); in em_sti_clock_event_next()
293 return !safe; in em_sti_clock_event_next()
/linux-4.1.27/arch/x86/realmode/rm/
Dtrampoline_32.S39 cli # We should be safe anyway
Dtrampoline_64.S40 cli # We should be safe anyway
/linux-4.1.27/drivers/input/gameport/
Dns558.c274 struct ns558 *ns558, *safe; in ns558_exit() local
276 list_for_each_entry_safe(ns558, safe, &ns558_list, node) { in ns558_exit()
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Dcrossbar.txt28 - ti,irqs-safe-map: integer which maps to a safe configuration to use
/linux-4.1.27/fs/ocfs2/
DKconfig36 It is always safe to say Y here, as the clustering method is
48 It is safe to say Y, as the clustering method is run-time
/linux-4.1.27/arch/s390/boot/compressed/
Dhead.S30 # move the memory mover someplace safe
/linux-4.1.27/drivers/mtd/devices/
Dphram.c87 struct phram_mtd_list *this, *safe; in unregister_devices() local
89 list_for_each_entry_safe(this, safe, &phram_list, list) { in unregister_devices()
/linux-4.1.27/net/tipc/
Dnode.c201 struct tipc_sock_conn *conn, *safe; in tipc_node_remove_conn() local
211 list_for_each_entry_safe(conn, safe, &node->conn_sks, list) { in tipc_node_remove_conn()
372 struct tipc_sock_conn *conn, *safe; in node_lost_contact() local
418 list_for_each_entry_safe(conn, safe, conns, list) { in node_lost_contact()
Dserver.c431 struct outqueue_entry *e, *safe; in tipc_clean_outqueues() local
434 list_for_each_entry_safe(e, safe, &con->outqueue, list) { in tipc_clean_outqueues()
Dname_table.c806 struct publication *publ, *safe; in tipc_purge_publications() local
813 list_for_each_entry_safe(publ, safe, &info->zone_list, zone_list) { in tipc_purge_publications()
/linux-4.1.27/arch/cris/arch-v32/
DKconfig200 stuff. If you don't know what to use, it is always safe to put all
222 stuff. If you don't know what to use, it is always safe to put all
244 stuff. If you don't know what to use, it is always safe to put all
266 stuff. If you don't know what to use, it is always safe to put all
288 stuff. If you don't know what to use, it is always safe to put all
/linux-4.1.27/fs/efs/
DKconfig10 what all this is about, it's safe to say N. For more information
/linux-4.1.27/kernel/debug/kdb/
Dkdb_cmds5 # be safe. Global breakpoint commands affect each cpu as it is booted.
/linux-4.1.27/drivers/staging/iio/trigger/
DKconfig24 If unsure, say N (but it's safe to say "Y").
/linux-4.1.27/Documentation/prctl/
Dno_new_privs.txt18 new, generic mechanism to make it safe for a process to modify its
55 several options to unshare(2) and clone(2) would be safe when
/linux-4.1.27/drivers/scsi/arm/
DKconfig21 implement this properly, so the safe answer is N.
31 don't implement it properly, so the safe answer is N.
/linux-4.1.27/drivers/iio/trigger/
DKconfig23 If unsure, say N (but it's safe to say "Y").
/linux-4.1.27/arch/ia64/scripts/
Dtoolchain-flags23 please upgrade to a newer version (it is safe to use this linker, but
/linux-4.1.27/drivers/net/wireless/b43/
DKconfig21 It is safe to include both b43 and b43legacy as the underlying glue
90 It's safe to select Y here, even if you don't have a B43 PCMCIA device.
107 It's safe to select Y here, even if you don't have a B43 SDIO device.
/linux-4.1.27/drivers/net/wimax/i2400m/
DKconfig19 If unsure, it is safe to select M (module).
/linux-4.1.27/scripts/coccinelle/free/
Difnullfree.cocci4 /// "kfree(NULL) is safe this check is probably not required"
/linux-4.1.27/net/wimax/
DKconfig22 If unsure, it is safe to select M (module).
/linux-4.1.27/drivers/staging/android/ion/
DKconfig10 If you're not using Android its probably safe to
/linux-4.1.27/arch/sparc/kernel/
Dwof.S110 wr %glob_tmp, 0x0, %wim ! set new %wim, this is safe now
147 wr %glob_tmp, 0x0, %wim ! Now it is safe to set new %wim
/linux-4.1.27/drivers/staging/iio/adc/
DKconfig47 If unsure, say N (but it's safe to say "Y").
67 If unsure, say N (but it's safe to say "Y").
/linux-4.1.27/arch/x86/um/
DKconfig54 N (on x86-64 it's automatically enabled, instead, as it's safe there).
/linux-4.1.27/Documentation/power/regulator/
Ddesign.txt18 specific knowledge that these changes are safe to perform on this
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds240622 respectively. Bits 2-7 are ignored, so it's safe to write ASCII data.
/linux-4.1.27/lib/fonts/
DKconfig21 If unsure, say N (the default choices are safe).
35 here is safe.
/linux-4.1.27/Documentation/infiniband/
Dcore_locking.txt40 are therefore safe to call from any context.
47 the midlayer is also safe to call from any context.
Duser_verbs.txt67 and so on. Since the InfiniBand userspace verbs should be safe for
Dipoib.txt90 is safe to enable this option with debug_level set to 0 for normal
/linux-4.1.27/drivers/isdn/hardware/eicon/
Dum_idi.c105 struct list_head *tmp, *safe; in diva_user_mode_idi_finit() local
108 list_for_each_safe(tmp, safe, &adapter_q) { in diva_user_mode_idi_finit()
171 struct list_head *tmp, *safe; in cleanup_adapter() local
174 list_for_each_safe(tmp, safe, &a->entity_q) { in cleanup_adapter()
/linux-4.1.27/tools/perf/scripts/perl/
Drwtop.pl96 $sa->safe(1);
/linux-4.1.27/Documentation/networking/
Dsctp.txt25 module removal of lksctp is not yet a safe activity.
Di40e.txt54 other protocols besides TCP. It's also safe to use with configurations that
Ds2io.txt134 recommended as safe parameters.
Dphy.txt20 management bus, it is difficult to ensure safe use of the bus.
48 time, so it is safe for them to block, waiting for an interrupt to signal
Dipvs-sysctl.txt36 bit 1: enable rescheduling of new connections when it is safe.
/linux-4.1.27/Documentation/arm/
Dcluster-pm-race-avoidance.txt28 cluster-level operations are only performed when it is truly safe to do
36 methods of coordination are required in order to guarantee safe
166 When a CPU reaches the CPU_UP state, it is safe for the CPU to
173 CPU is coherent yet, but it does mean that it is safe to resume
209 In order to enable safe coordination in such situations, it is important
472 is needed for safe transitions at the cluster level.
DBooting132 A safe location is just above the 128MiB boundary from start of RAM.
145 A safe location is just above the device tree blob which itself will
Dkernel_user_helpers.txt36 safe to call any particular helper. This check should ideally be
/linux-4.1.27/Documentation/filesystems/cifs/
Dcifs.txt16 performance safe distributed caching (oplock), optional packet
/linux-4.1.27/arch/frv/include/asm/
Datomic.h23 #error not SMP safe
/linux-4.1.27/Documentation/RCU/
Dlockdep.txt82 This expression picks up the pointer "fdt->fd[fd]" in an RCU-safe manner,
90 In case (1), the pointer is picked up in an RCU-safe manner for vanilla
DUP.txt89 It -is- safe for synchronize_sched() and synchronize_rcu_bh() to return
90 immediately on an UP system. It is also safe for synchronize_rcu()
Drcu_dereference.txt50 "p+a-b" is safe because its value still necessarily depends on
140 it is safe to compare pointers from rcu_dereference()
152 this is safe is that even if misordering occurs, the
203 safe on strongly ordered systems (such as x86), but not on weakly
DNMI-RCU.txt94 not to return until all ongoing NMI handlers exit. It is therefore safe
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-regulator152 min_microvolts. This holds the minimum safe working regulator
167 max_microvolts. This holds the maximum safe working regulator
182 min_microamps. This holds the minimum safe working regulator
197 max_microamps. This holds the maximum safe working regulator
/linux-4.1.27/drivers/iio/adc/
DKconfig55 If unsure, say N (but it's safe to say "Y").
67 N (but it is safe to say "Y").
79 If unsure, say N (but it's safe to say "Y").
92 If unsure, say N (but it's safe to say "Y").
/linux-4.1.27/Documentation/cpu-freq/
Damd-powernow.txt8 so it is safe to try each driver in turn when in doubt as to
/linux-4.1.27/drivers/net/ethernet/alteon/
DKconfig46 The safe and default value for this is N.
/linux-4.1.27/Documentation/
Dgdb-kernel-debugging.txt49 Note: Some distros may restrict auto-loading of gdb scripts to known safe
52 add-auto-load-safe-path /path/to/linux-build
Dthis_cpu_ops.txt211 this_cpu ops are interrupt safe. Some architectures do not support
222 and the scheduler cannot preempt, then they are safe. If any interrupts
225 safe.
271 structures remotely. It is usually safe to do a remote read access
Dio_ordering.txt4 typically done by reading a 'safe' device or bridge register, causing the I/O
Dpreempt-locking.txt49 Note, some FPU functions are already explicitly preempt safe. For example,
113 This code is not preempt-safe, but see how easily we can fix it by simply
Dkselftest.txt10 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
Dlocal_ops.txt33 sure that we modify it from within a preemption safe context. It is however
95 If you are already in a preemption-safe context, you can use
Dhighuid.txt70 (it should be safe because it's always used a 32-bit integer to
Dkernel-per-CPU-kthreads.txt192 make sure that this is safe on your particular system.
217 make sure that this is safe on your particular system.
222 make sure that this is safe on your particular system.
Dvolatile-considered-harmful.txt19 safe (spinlocks, mutexes, memory barriers, etc.) are designed to prevent
Dkasan.txt145 of kmemcheck: use shadow memory to record whether each byte of memory is safe
Dvgaarbiter.txt156 card can be left out of the arbitration process (and can be safe to take
Dkref.txt47 holding a valid pointer, it is safe to do this without
Dvfio.txt10 safe[2], non-privileged, userspace drivers.
436 [2] "safe" also depends upon a device being "well behaved". It's
/linux-4.1.27/arch/ia64/sn/kernel/
Dio_common.c367 struct list_head *list, *safe; in sn_bus_free_sysdata() local
369 list_for_each_safe(list, safe, &sn_sysdata_list) { in sn_bus_free_sysdata()
/linux-4.1.27/drivers/pci/pcie/
DKconfig41 hardware or configurations and enable it when known-safe.
/linux-4.1.27/fs/ufs/
DKconfig28 If you haven't heard about all of this before, it's safe to say N.
/linux-4.1.27/fs/sysv/
DKconfig36 If you haven't heard about all of this before, it's safe to say N.
/linux-4.1.27/Documentation/ia64/
Daliasing.txt130 identity mapping. This is obviously safe for things in
177 so it is safe to use WB mappings.
194 safe attribute to use.
Dfsys.txt134 it is not safe to assume that user-level called a handler with the
138 unless proper safe-guards are taken (e.g., interruptions are avoided),
213 restart is still safe. If the system call number is invalid,
/linux-4.1.27/Documentation/cgroups/
Dcpuacct.txt46 This is because percpu_counter_read() on 32bit systems isn't safe
/linux-4.1.27/drivers/s390/char/
DKconfig152 It is safe to say "Y" here.
161 It is safe to say "Y" here.
/linux-4.1.27/Documentation/power/
Ddrivers-testing.txt46 regarded as suspend/resume-safe.
Dsuspend-and-interrupts.txt130 IRQF_NO_SUSPEND user. In order for this to be safe, the wakeup device driver
Dcharger-manager.txt173 : This callback returns 0 if the temperature is safe for charging,
Druntime_pm.txt73 the PM core that it is safe to run the ->runtime_suspend(), ->runtime_resume()
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
497 It is safe to execute the following helper functions from interrupt context:
/linux-4.1.27/drivers/gpu/drm/
Ddrm_prime.c169 struct drm_prime_member *member, *safe; in drm_prime_remove_buf_handle_locked() local
171 list_for_each_entry_safe(member, safe, &prime_fpriv->head, entry) { in drm_prime_remove_buf_handle_locked()
/linux-4.1.27/drivers/s390/block/
DKconfig53 Select this option to be able to access FBA devices. It is safe to
Dscm_blk.c52 struct list_head *iter, *safe; in scm_free_rqs() local
56 list_for_each_safe(iter, safe, &inactive_requests) { in scm_free_rqs()
/linux-4.1.27/arch/metag/
DKconfig153 is not SMP-safe.
212 of the DA will be detected automatically at boot, so it is safe to say
/linux-4.1.27/drivers/net/ppp/
DKconfig46 it is safe to say Y here.
67 they don't support it, it is safe to say Y here.
/linux-4.1.27/drivers/net/wireless/b43legacy/
DKconfig13 It is safe to include both b43 and b43legacy as the underlying glue
/linux-4.1.27/Documentation/fb/
Dsstfb.txt138 - The driver is not your_favorite_toy-safe. this includes SMP...
139 [Actually from inspection it seems to be safe - Alan]
Dvesafb.txt140 is the safe (and slow) default.
Dudlfb.txt156 period of time (one minute or less is safe).
Dintel810.txt239 safe side, you can leave this unselected.
/linux-4.1.27/include/linux/
Dcompiler.h9 # define __safe __attribute__((safe))
Duwb.h115 int safe; member
/linux-4.1.27/drivers/s390/net/
DKconfig12 If you do not know what it is, it's safe to choose Y.
/linux-4.1.27/Documentation/gpio/
Dconsumer.txt152 for spinlock-safe GPIOs it is OK to use them before tasking is enabled, as part
210 IRQ handler, and those accessors must be used instead of spinlock-safe
215 spinlock-safe calls.
Dgpio-legacy.txt141 a task context. However, for spinlock-safe GPIOs it's OK to use them
219 spinlock-safe accessors without the cansleep() name suffix.
223 the same as the spinlock-safe calls.
258 a task context. However, for spinlock-safe GPIOs it's OK to request GPIOs
266 signal, or (b) something wrongly believes it's safe to remove drivers
/linux-4.1.27/arch/unicore32/
DKconfig164 configuration it is safe to say N, otherwise say Y.
/linux-4.1.27/fs/ext3/
DKconfig48 data=ordered mode will be a safe choice and you should
/linux-4.1.27/Documentation/scheduler/
Dcompletion.txt133 uninterruptible. wait_for_completion() and its variants are only safe
247 Both try_wait_for_completion() and completion_done() are safe to be called in
/linux-4.1.27/arch/blackfin/
DKconfig.debug49 On production systems, it is safe (and a small optimization) to say N.
207 command line (bootargs). It is safe to say Y here in all cases, as
DKconfig962 interrupt latency issues, it is safe and OK to turn this off.
1070 cache is updated. This is a completely safe setting, but
1073 If you are unsure of the options and you want to be safe,
1087 cache is updated. This is a completely safe setting, but
1090 If you are unsure of the options and you want to be safe,
/linux-4.1.27/arch/ia64/
DKconfig221 types of ia64 systems. If you have an SGI Altix system, it's safe
233 types of ia64 systems. If you have an SGI UV system, it's safe
252 This choice is safe for all IA-64 systems, but may not perform
/linux-4.1.27/sound/oss/
DKconfig308 safe to answer Y if you have the original Windows Sound System card
345 is safe to answer Y if you have a true MPU401 MIDI interface card.
441 Answering Y is usually a safe and recommended choice, however some
456 UART chip. This interface is rarely found on sound cards. It's safe
/linux-4.1.27/arch/arm/nwfpe/
DChangeLog70 completeness (better safe than sorry).
/linux-4.1.27/fs/gfs2/
Dlog.c279 struct gfs2_trans *tr, *safe; in ail2_empty() local
286 list_for_each_entry_safe(tr, safe, &sdp->sd_ail2_list, tr_list) { in ail2_empty()
/linux-4.1.27/drivers/block/
DKconfig235 bits of, say, a sound file). This is also safe if the file resides
244 the cryptoloop is not safe for storing journaled filesystems.
279 WARNING: This device is not safe for journaled file systems like
319 don't have one of these, it is safe to answer N.
/linux-4.1.27/Documentation/x86/
Dentry_64.txt90 stack but before we executed SWAPGS, then the only safe way to check
Dboot.txt27 safe for systems which use the EBDA from SMM or 32-bit
208 (3) Ignored, but safe to set, for boot protocols 2.02-2.09.
510 Kernels prior to 2.6.31 did not recognize this field, but it is safe
524 Kernels prior to 2.6.31 did not recognize this field, but it is safe
551 address is defined as the address of the highest safe byte, so if
727 be used by a relocating boot loader to help select a safe load
/linux-4.1.27/arch/arm/plat-omap/
DKconfig90 printed, it's safe to deselect OMAP_MUX for your product.
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dmax8997-regulator.txt28 safe operating voltage).
Ds5m8767-regulator.txt31 safe operating voltage).
/linux-4.1.27/Documentation/i2c/
Dfunctionality148 /* Now it is safe to use the SMBus write_quick command */
Ddev-interface117 the adapter has I2C_FUNC_SMBUS_PEC; it is still safe if not, it just
/linux-4.1.27/arch/arm/kernel/
Dentry-armv.S326 @ save/restore lr_abt and spsr_abt to make nested aborts safe.
336 mrs r2, spsr @ Save spsr_abt, abort is now safe
/linux-4.1.27/arch/cris/arch-v10/
DKconfig333 stuff. If you don't know what to use, it is always safe to put all
362 If you don't know what to use, it is always safe to put all as
/linux-4.1.27/drivers/isdn/i4l/
DKconfig57 it is safe to say Y here.
/linux-4.1.27/Documentation/i2c/busses/
Di2c-piix4106 of all affected systems, so the only safe solution was to prevent access to
Di2c-i801150 and seems safe, please submit a patch for inclusion into the kernel.
/linux-4.1.27/Documentation/trace/
Dtracepoints.txt98 probe call, make sure that probe removal and module unload are safe.
Dmmiotrace.txt25 disabled by default, so it is safe to have this set to yes. SMP systems are
/linux-4.1.27/arch/mips/
DKconfig1339 otherwise CPU_MIPS32_R1 is a safe bet for any MIPS32 system.
1358 otherwise CPU_MIPS32_R1 is a safe bet for any MIPS32 system.
1389 otherwise CPU_MIPS64_R1 is a safe bet for any MIPS64 system.
1409 otherwise CPU_MIPS64_R1 is a safe bet for any MIPS64 system.
1438 might be a safe bet. If the resulting kernel does not work,
2238 no external assistance. It is safe to enable this when hardware
2361 # where it's known to be safe. This will not offer highmem on a few systems
2363 # indexed CPUs but we're playing safe.
2639 and the task is only allowed to execute a few safe syscalls
/linux-4.1.27/Documentation/devicetree/bindings/gpu/
Dnvidia,tegra20-host1x.txt211 - safe: safe reference for the SOR clock during power up
/linux-4.1.27/Documentation/virtual/kvm/
Dlocking.txt28 is safe because whenever changing these bits can be detected by cmpxchg.
Dppc-pv.txt122 The following bits are safe to be set inside the guest:
Dmsr.txt250 It is always safe for the guest to ignore the optimization and perform
/linux-4.1.27/drivers/scsi/
DKconfig898 such as a printer; it is safe to compile both drivers into the
925 such as a printer; it is safe to compile both drivers into the
932 bool "ppa/imm option - Use slow (but safe) EPP-16"
944 Generally, saying Y is the safe option and slows things down a bit.
991 have a Lasi chip, it is safe to say "Y" here.
1165 There is no safe option other than using good SCSI devices.
1182 There is no safe option and the default answer is recommended.
1215 There is no safe option other than using good cabling, right
1499 usually rated at 5 MB/s. 5 is a safe value here unless you know the
/linux-4.1.27/drivers/net/ethernet/dec/tulip/
DKconfig39 cache coherence, an example is PowerMac 5500. Otherwise 0 is safe.
/linux-4.1.27/include/linux/ceph/
Dceph_fs.h428 __u8 safe; /* true if committed to disk */ member
/linux-4.1.27/arch/arc/mm/
Dtlbex.S55 ; exception prologue (IRQ auto-disabled on Exceptions, so it's IRQ-safe).
/linux-4.1.27/drivers/cpufreq/
DKconfig.arm82 It requires, for safe operation, thermal framework with properly
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmc.txt34 - cap-power-off-card: powering off the card is safe
/linux-4.1.27/Documentation/console/
Dconsole.txt126 false(), then it's safe to release the resources. This balance has to be
/linux-4.1.27/Documentation/usb/
Ddma.txt110 buffers, synchronizing their safe re-use. (If there's no re-use, then let
Dpersist.txt26 though they had disconnected. This is always safe and it is the
/linux-4.1.27/Documentation/vm/
Dhwpoison.txt18 * that if the error cannot be handled for some reason it's safe to
/linux-4.1.27/Documentation/powerpc/
Dpmu-ebb.txt47 It is however safe to run 'perf' commands on a process which is using EBBs. The
/linux-4.1.27/arch/
DKconfig321 - secure_computing is called from a ptrace_event()-safe context
329 need to be called from a ptrace-safe context. It must then
/linux-4.1.27/arch/arm/mach-davinci/
DKconfig244 printed, it's safe to deselect DAVINCI_MUX for your product.
/linux-4.1.27/arch/microblaze/
DKconfig124 and the task is only allowed to execute a few safe syscalls
/linux-4.1.27/drivers/char/
DKconfig80 If unsure, it is safe to say Y.
105 (e.g. printer and ZIP drive) and it is safe to compile the
147 It is safe to say N to this -- it is not needed for normal printing
/linux-4.1.27/arch/parisc/
DKconfig336 and the task is only allowed to execute a few safe syscalls
/linux-4.1.27/arch/m68k/fpsp040/
Dstan.S318 |--safe.
/linux-4.1.27/Documentation/filesystems/
Dtmpfs.txt121 NUMA capability (perhaps a safe recovery kernel), or with fewer nodes
Dext3.txt70 safe to use, at some performance penalty. If
Dporting215 ->d_parent changes are not protected by BKL anymore. Read access is safe
255 it's safe to remove it. If you don't need it, remove it.
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-driver-ib_srp55 only safe with partial memory descriptor list support enabled
/linux-4.1.27/drivers/usb/storage/
DKconfig211 If you don't know whether you have a UAS device, it is safe to
/linux-4.1.27/Documentation/sound/oss/
DPAS16117 Answering Y is usually a safe and recommended choice, however some
/linux-4.1.27/Documentation/laptops/
Ddisk-shock-protection.txt109 feature nonetheless. Unfortunately, there is no safe way Linux can
/linux-4.1.27/Documentation/video4linux/
Dvideobuf62 need to be an interrupt-safe spinlock which is used to protect (at least)
169 structure for this video device, irqlock is an interrupt-safe spinlock to
/linux-4.1.27/arch/sh/
DKconfig648 where the fail safe kernel needs to run at a different address
662 allowed to execute a few safe syscalls defined by each seccomp
/linux-4.1.27/drivers/input/touchscreen/
DKconfig44 If unsure, say N (but it's safe to say "Y").
57 If unsure, say N (but it's safe to say "Y").
88 If unsure, say N (but it's safe to say "Y").
/linux-4.1.27/fs/cifs/
DKconfig34 safe distributed caching (oplock), optional packet
/linux-4.1.27/Documentation/sound/alsa/
Dhdspm.txt79 safe pointer for writing, which is used on this mode inside
/linux-4.1.27/net/mac80211/
DKconfig131 of function calls in the code, but is otherwise safe to
/linux-4.1.27/fs/ceph/
Dmds_client.c2374 if ((req->r_got_unsafe && !head->safe) || in handle_reply()
2375 (req->r_got_safe && head->safe)) { in handle_reply()
2377 head->safe ? "safe" : "unsafe", tid, mds); in handle_reply()
2381 if (req->r_got_safe && !head->safe) { in handle_reply()
2419 if (head->safe) { in handle_reply()
/linux-4.1.27/arch/s390/
DKconfig336 executing 31 bit applications. It is safe to say "Y".
626 and the task is only allowed to execute a few safe syscalls
/linux-4.1.27/drivers/tty/
DKconfig149 systems, it is safe to say N.
225 If you haven't heard about it, it's safe to say N.
/linux-4.1.27/Documentation/security/
Dkeys.txt1198 It is safe to sleep in this method.
1223 It is safe to sleep in this method.
1283 It is safe to sleep in this method, though care should be taken to avoid
1296 It is not safe to sleep in this method; the caller may hold spinlocks.
1311 It is not safe to sleep in this method; the RCU read lock is held by the
1327 when accessing the key's payload. It is safe to sleep in this method, such
/linux-4.1.27/fs/reiserfs/
DREADME149 the endian safe patches which allow ReiserFS to run on any platform
/linux-4.1.27/drivers/input/serio/
DKconfig126 It's safe to enable this driver, so if unsure, say Y.
/linux-4.1.27/fs/affs/
DChanges80 - locking should be safe for the future
/linux-4.1.27/arch/arc/kernel/
Dentry.S619 ; !CONFIG_PREEMPT: To ensure restore_regs is intr safe
/linux-4.1.27/drivers/scsi/sym53c8xx_2/
Dsym_glue.c73 module_param_named(safe, safe_string, charp, 0);
87 MODULE_PARM_DESC(safe, "Set other settings to a \"safe mode\"");
/linux-4.1.27/arch/powerpc/platforms/
DKconfig167 to not read back properly. It is safe to use on other chips as
/linux-4.1.27/drivers/usb/misc/
DKconfig149 It is safe to say M here.
/linux-4.1.27/drivers/macintosh/
DKconfig72 models should use CONFIG_ADB_PMU instead. It is safe to say Y here
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt143 NMI-safe and return a sane value in any context.
/linux-4.1.27/arch/powerpc/
DKconfig.debug256 kernel BSS and should be safe to select on any system. A debugger

12