/linux-4.1.27/net/batman-adv/ |
D | Kconfig | 26 more than one mesh node in the same LAN, you can safely remove 37 this option you can safely remove it and save some space. 51 can safely disable it and save some space.
|
/linux-4.1.27/Documentation/hwmon/ |
D | ltc4260 | 17 The LTC4260 Hot Swap controller allows a board to be safely inserted 25 which can be safely used to identify the chip. You will have to instantiate
|
D | ltc4261 | 18 to be safely inserted and removed from a live backplane. 25 which can be safely used to identify the chip. You will have to instantiate
|
D | ltc4151 | 24 which can be safely used to identify the chip. You will have to instantiate
|
D | ltc4215 | 17 The LTC4215 controller allows a board to be safely inserted and removed
|
D | lineage-pem | 30 which can be safely used to identify the chip. You will have to instantiate
|
D | ltc2945 | 25 which can be safely used to identify the chip. You will have to instantiate
|
D | ltc4245 | 17 The LTC4245 controller allows a board to be safely inserted and removed
|
D | max16065 | 61 can be safely used to identify the chip. You will have to instantiate
|
D | k10temp | 58 are using an AM3 processor on an AM2+ mainboard, you can safely use the
|
D | smm665 | 62 can be safely used to identify the chip. You will have to instantiate
|
D | pmbus | 56 which can be safely used to identify the chip (The MFG_ID register is not
|
/linux-4.1.27/drivers/net/ethernet/nxp/ |
D | Kconfig | 7 some NXP LPC devices. You can safely enable this option for LPC32xx
|
/linux-4.1.27/arch/blackfin/mach-common/ |
D | arch_checks.c | 51 # error the MPU will not function safely while Anomaly 05000263 applies
|
/linux-4.1.27/Documentation/RCU/ |
D | rcuref.txt | 113 element can therefore safely be freed. This in turn guarantees that if 114 any reader finds the element, that reader may safely acquire a reference
|
D | arrayRCU.txt | 96 that it may later safely be dereferenced -- memory barriers are
|
D | rcu.txt | 37 safely free up that item.
|
D | rcubarrier.txt | 40 Since call_rcu() never blocks, this code can safely be used from within 272 so that your module may be safely unloaded.
|
D | whatisRCU.txt | 81 to the data structure, so it now may safely be reclaimed 217 RCU-protected pointer, in order to safely communicate the change 236 pointer, which returns a value that may then be safely 666 to that data item, so we can safely reclaim it.
|
D | checklist.txt | 349 to safely access and/or modify that data structure. 408 readers will execute safely.
|
D | rcu_dereference.txt | 6 subtraction of constants, and casts all work quite naturally and safely.
|
D | RTFP.txt | 1247 First posting showing how RCU can be safely adapted for
|
/linux-4.1.27/drivers/net/ethernet/toshiba/ |
D | Kconfig | 41 safely enable this option even if you have a wireless-less model.
|
/linux-4.1.27/Documentation/watchdog/ |
D | wdt.txt | 23 The ICS ISA-bus wdt card cannot be safely probed for. Instead you need to
|
/linux-4.1.27/Documentation/scheduler/ |
D | completion.txt | 25 can continue safely. 124 so it can only be called safely when you know that interrupts are enabled. 220 complete() and complete_all() can be called in hard-irq/atomic context safely.
|
D | sched-deadline.txt | 118 * The reader can "safely" skip to Section 4 if only interested in seeing
|
/linux-4.1.27/Documentation/arm/ |
D | cluster-pm-race-avoidance.txt | 6 controls safely. 307 safely. 317 enabled for the cluster. Other CPUs in the cluster can safely 332 enabled for the cluster. Other CPUs in the cluster can safely 425 be used to select a last man safely, before the CPUs become
|
/linux-4.1.27/Documentation/gpio/ |
D | consumer.txt | 172 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ 188 Also, using these calls for GPIOs that can't safely be accessed without sleeping 334 The GPIO number returned by desc_to_gpio() can be safely used as long as the
|
D | gpio-legacy.txt | 163 Those don't need to sleep, and can safely be done from inside hard 183 return zero. Also, using these calls for GPIOs that can't safely be accessed
|
/linux-4.1.27/Documentation/infiniband/ |
D | core_locking.txt | 62 example, a consumer may safely call ib_poll_cq() on multiple CPUs
|
/linux-4.1.27/Documentation/ia64/ |
D | aliasing.txt | 69 can referenced safely by an identity mapping. 153 region safely with kernel page table mappings, we can use
|
/linux-4.1.27/Documentation/firmware_class/ |
D | README | 125 request_firmware can be called safely inside device's suspend and
|
/linux-4.1.27/Documentation/networking/ |
D | radiotap-headers.txt | 118 * iterator.this_arg for type "type" safely on all arches.
|
D | xfrm_sync.txt | 7 events so that the an SA can be safely moved from one machine to another
|
D | arcnet-hardware.txt | 45 ARCnet will guarantee that a packet arrives safely at the destination, and 299 always be safely disabled, if your video card supports it at all.
|
D | ip-sysctl.txt | 711 invalidated when required when means you can safely toggle this on and
|
D | bonding.txt | 1556 can safely be sent over either interface. Such configurations may be achieved
|
/linux-4.1.27/Documentation/misc-devices/ |
D | lis3lv02d | 87 Q: How do I safely simulate freefall? I have an HP "portable
|
/linux-4.1.27/Documentation/x86/x86_64/ |
D | kernel-stacks | 50 nested. For example, a debug interrupt can safely be interrupted by an
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | nfs.txt | 48 changed safely if care is taken that the client shuts down cleanly and all
|
/linux-4.1.27/arch/blackfin/ |
D | Kconfig | 684 safely write to the 'cycles' register during runtime. You will 712 safely use NMI on the Blackfin while running Linux, but 723 safely use a JTAG ICE while debugging a Blackfin board, 724 but you can safely use the CYCLES performance registers 734 safely use the CYCLES performance registers on a Blackfin
|
/linux-4.1.27/Documentation/sound/oss/ |
D | PSS-updates | 47 parameter and with the parameter below set to true then a user can safely unload
|
/linux-4.1.27/Documentation/filesystems/ |
D | devpts.txt | 27 can safely be ignored.
|
D | ext3.txt | 72 disabling barriers may safely improve performance.
|
D | ext2.txt | 229 It safely allows features to be added to the filesystem, without
|
D | ext4.txt | 194 disabling barriers may safely improve performance.
|
D | vfs.txt | 236 noted. This means that most methods can block safely. All methods are
|
D | proc.txt | 749 clue as to how big an area you can safely allocate, or why a previous
|
/linux-4.1.27/Documentation/power/ |
D | opp.txt | 57 This initial list contains a set of OPPs that the framework expects to be safely 65 SoC framework might choose to disable a higher frequency OPP to safely continue
|
D | devices.txt | 332 safely leave the device in runtime suspend (if runtime-suspended
|
/linux-4.1.27/arch/m68k/q40/ |
D | README | 12 It seems IRQ unmasking can't be safely done on a Q40. IRQ probing
|
/linux-4.1.27/Documentation/usb/ |
D | dma.txt | 90 driver can safely be used with such DMA mapping. (See the first section
|
D | WUSB-Design-overview.txt | 209 takes time of tearing everything down safely (or not...).
|
/linux-4.1.27/arch/microblaze/ |
D | Kconfig | 113 bool "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/Documentation/ |
D | magic-number.txt | 26 discipline, these cases get detected quickly and safely.
|
D | email-clients.txt | 136 You can safely GPG sign attachments, but inlined text is preferred for
|
D | robust-futexes.txt | 36 the lock can be recovered safely.
|
D | kobject.txt | 39 safely ignore that implementation detail as the kset core code handles
|
D | md.txt | 460 recorded to disk safely) bad blocks.
|
D | kprobes.txt | 472 the bad probe, are safely unregistered before the register_*probes
|
D | DMA-API-HOWTO.txt | 924 an architecture port for the kernel, you can safely skip down
|
D | kernel-parameters.txt | 3933 emulated reasonably safely.
|
/linux-4.1.27/Documentation/connector/ |
D | connector.txt | 78 Sends message to the specified groups. It can be safely called from
|
/linux-4.1.27/arch/parisc/ |
D | Kconfig | 327 prompt "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/Documentation/metag/ |
D | kernel-ABI.txt | 243 If the function hasn't touched the frame pointer, MGETL cannot be safely used
|
/linux-4.1.27/Documentation/fb/ |
D | intel810.txt | 194 supports I2C and has an EDID block, you can safely exclude hsync1, hsync2,
|
/linux-4.1.27/fs/ubifs/ |
D | tnc.c | 1433 int found, n, err, safely = 0, gc_seq1; in ubifs_tnc_locate() local 1460 if (safely) { in ubifs_tnc_locate() 1481 safely = 1; in ubifs_tnc_locate()
|
/linux-4.1.27/Documentation/blockdev/ |
D | floppy.txt | 170 interrupts affect only performance, and can be safely ignored.)
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | timestamping.txt | 93 safely.
|
D | hda_codec.txt | 192 All are non-NULL, so you can call them safely without NULL check.
|
D | Audiophile-Usb.txt | 314 You may safely skip this section if you're not interested in driver
|
/linux-4.1.27/Documentation/hid/ |
D | uhid.txt | 147 You can usually ignored any UHID_STOP events safely.
|
/linux-4.1.27/Documentation/timers/ |
D | highres.txt | 175 is restricted to code which can safely be executed in the hard interrupt
|
/linux-4.1.27/arch/sparc/ |
D | Kconfig | 237 bool "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/Documentation/scsi/ |
D | ChangeLog.sym53c8xx | 553 current 896 rev.1 seems not to operate safely with the driver 559 driver to safely enable hardware phase mismatch with 896 rev. 1.
|
D | sym53c8xx_2.txt | 404 this feature after boot-up only for devices that support it safely. 517 You can play safely with DEBUG_NEGO. However, some of these flags may
|
D | ncr53c8xx.txt | 563 this feature after boot-up only for devices that support it safely. 750 You can play safely with DEBUG_NEGO. However, some of these flags may
|
D | scsi_mid_low_api.txt | 451 * slave_destroy().] Can safely be invoked from interrupt code.
|
/linux-4.1.27/scripts/ |
D | spelling.txt | 843 safly||safely
|
/linux-4.1.27/sound/oss/ |
D | CHANGELOG | 57 You can safely use this driver version with C930 if it looks to work.
|
/linux-4.1.27/arch/x86/ |
D | Kconfig | 740 You can safely choose Y here. However, HPET will only be 1045 This adds a driver to safely access the System Management Mode of 1061 This adds a driver to safely access the System Management Mode 1559 You can safely say Y even if your machine doesn't have MTRRs, you'll 1702 prompt "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/arch/sh/ |
D | Kconfig | 652 bool "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/Documentation/vm/ |
D | frontswap.txt | 85 that can be safely kept in RAM. Zcache essentially trades off CPU
|
/linux-4.1.27/Documentation/input/ |
D | multi-touch-protocol.txt | 328 devices do not have blob capability, so drivers can safely omit this event.
|
/linux-4.1.27/arch/s390/ |
D | Kconfig | 616 prompt "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/arch/arm64/ |
D | Kconfig | 584 bool "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/drivers/regulator/ |
D | Kconfig | 17 This framework safely compiles out if not selected so that client
|
/linux-4.1.27/net/ipv4/ |
D | Kconfig | 459 Nearly all users can safely say no here, and a safe default
|
/linux-4.1.27/Documentation/netlabel/ |
D | draft-ietf-cipso-ipsecurity-01.txt | 615 the system administrator to identify tag types that may safely be
|
/linux-4.1.27/Documentation/video4linux/ |
D | v4l2-controls.txt | 370 or set a single control value safely in your driver:
|
D | v4l2-framework.txt | 881 Note that you can safely call video_set_drvdata() before calling
|
/linux-4.1.27/arch/powerpc/ |
D | Kconfig | 682 bool "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/drivers/scsi/aic7xxx/ |
D | aic7xxx.reg | 234 * the data has been safely transferred. SDONE in SSTAT0 is
|
D | aic7xxx.seq | 362 * when we have outstanding transactions, so we can safely
|
D | aic79xx.seq | 1913 * are not performing a pointer save, we can safely clear the channel
|
/linux-4.1.27/Documentation/sysctl/ |
D | kernel.txt | 223 /proc/pid directory. In order to do this safely, the kernel must wait
|
/linux-4.1.27/scripts/genksyms/ |
D | parse.tab.c_shipped | 330 and a page size can be as small as 4096 bytes. So we cannot safely
|
/linux-4.1.27/scripts/kconfig/ |
D | zconf.tab.c_shipped | 320 and a page size can be as small as 4096 bytes. So we cannot safely
|
/linux-4.1.27/scripts/dtc/ |
D | dtc-parser.tab.c_shipped | 332 and a page size can be as small as 4096 bytes. So we cannot safely
|
/linux-4.1.27/Documentation/locking/ |
D | rt-mutex-design.txt | 671 Since the wait_lock was taken at the entry of the slow lock, we can safely
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | README | 180 such symlinks safely by converting unsafe symlinks (ie symlinks to server
|
D | CHANGES | 94 file to a temporary name). Add experimental support for more safely
|
/linux-4.1.27/drivers/rtc/ |
D | Kconfig | 750 you can safely enable this driver if you don't know whether
|
/linux-4.1.27/arch/mips/ |
D | Kconfig | 2628 bool "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/Documentation/block/ |
D | biodoc.txt | 924 request safely. The io scheduler may still
|
/linux-4.1.27/arch/arm/ |
D | Kconfig | 1736 prompt "Enable seccomp to safely compute untrusted bytecode"
|
/linux-4.1.27/init/ |
D | Kconfig | 294 running glibc can safely disable this.
|
/linux-4.1.27/drivers/video/fbdev/ |
D | Kconfig | 1914 single model of flatpanel then you can safely leave this
|
/linux-4.1.27/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 199 7. You can try new development kernels safely.
|