Home
last modified time | relevance | path

Searched refs:nothing (Results 1 – 192 of 192) sorted by relevance

/linux-4.1.27/tools/perf/tests/
Dmake158 # FIXME nothing gets installed
162 # FIXME nothing gets installed
166 # FIXME nothing gets installed
170 # FIXME nothing gets installed
174 # FIXME nothing gets installed
/linux-4.1.27/arch/arm/mach-vexpress/
Ddcscb_setup.S34 @ if any. In this case, there is nothing to do.
/linux-4.1.27/arch/sh/lib/
Dmemcpy.S17 bt/s 9f ! if n=0, do nothing
Dmemmove.S27 bt/s 9f ! if n=0, do nothing
Dmemset.S17 bt/s 5f ! if n=0, do nothing
/linux-4.1.27/drivers/staging/wlan-ng/
DREADME8 kernel developers about it, they want nothing to do with it.
/linux-4.1.27/drivers/block/drbd/
DKconfig19 DRBD is a shared-nothing, synchronously replicated block device. It
33 shared-nothing cluster. Needless to say, on top of dual-Primary
/linux-4.1.27/Documentation/sound/alsa/
DControlNames.txt6 <nothing> (both directions)
18 <nothing> (channel independent, or applies to all channels)
Demu10k1-jack.txt44 input, or nothing. The one exception is the SBLive! 5.1. On these devices,
Dhdspm.txt252 Switching on and off the analog out, which has nothing to do
DHD-Audio.txt393 config values by itself, this will contain nothing.
/linux-4.1.27/arch/mn10300/kernel/
Dprofile-low.S41 # do nothing if there's no buffer
/linux-4.1.27/Documentation/blockdev/drbd/
DREADME.txt3 DRBD is a shared-nothing, synchronously replicated block device. It
/linux-4.1.27/drivers/scsi/arm/
Dacornscsi-io.S21 @ Returns: nothing
76 @ Returns: nothing
/linux-4.1.27/drivers/bcma/
DREADME2 however from programming point of view there is nothing AMBA specific we use.
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dgpio-regulator.txt12 defualt is LOW if nothing is specified.
/linux-4.1.27/fs/gfs2/
Drecovery.c155 const u32 nothing = 0; in get_log_header() local
165 hash = crc32_le(hash, (unsigned char const *)&nothing, sizeof(nothing)); in get_log_header()
/linux-4.1.27/arch/parisc/include/asm/
Dhardware.h42 volatile uint32_t nothing; /* reg 0 */ member
/linux-4.1.27/Documentation/powerpc/
Dmpc52xx.txt35 nothing to do with the MPC5200. I also included the 'MPC' for the same
Dpci_iov_resource_on_powernv.txt268 respond to segments [0, total_VFs - 1]. There's nothing in hardware that
/linux-4.1.27/Documentation/RCU/
DNMI-RCU.txt20 nothing, but returns zero, thus saying that it did nothing, allowing
DwhatisRCU.txt242 it compiles to nothing, not even a compiler directive.
642 Note that rcu_read_lock() and rcu_read_unlock() do absolutely nothing.
Dtrace.txt439 o "nn" is the number of times that this CPU needed nothing.
DRTFP.txt35 At first glance, this has nothing to do with RCU, but nevertheless
/linux-4.1.27/drivers/staging/speakup/
Dvarhandlers.c88 static char nothing[2] = "\0"; in speakup_register_var() local
106 spk_set_string_var(nothing, p_header, 0); in speakup_register_var()
Dspkguide.txt153 reasons. This has nothing to do with Speakup, it's a Linux security
1230 (or to related matters) and contains nothing that could fall directly
1417 nothing but endorsements of your Modified Version by various
/linux-4.1.27/Documentation/usb/
Drio.txt34 down to nothing and appear to have corrupted the flash memory. My RIO
36 problem. Do NOT allow your batteries to wear down to nothing before
Dgadget_printer.txt13 the embedded OS. This driver has nothing to do with using a printer with
Dpersist.txt150 way to know you did it. The kernel will assume that nothing has
Dusb-serial.txt77 If after pressing the sync button, nothing shows up in the system log,
Dpower-management.txt103 Of course, nothing the kernel does on its own initiative should
/linux-4.1.27/arch/arm/mach-ep93xx/
Dcrunch-bits.S233 mov r0, #0 @ nothing to load
276 mov r0, #0 @ nothing to load
/linux-4.1.27/fs/sysv/
DKconfig28 nothing whatsoever to do with the option "System V IPC". Read about
/linux-4.1.27/Documentation/s390/
D3270.txt199 nothing. If you do nothing, the screen will clear in (default) 5 sec
200 and more output will appear. You may hit ENTER with nothing typed in
203 Running" and nothing typed, the application receives a newline.)
DDebugging390.txt418 up on function exit ( e.g. the caller may choose to allocate nothing
1299 read this instead. If nothing else you may find a few useful keywords in here
/linux-4.1.27/arch/arm/kernel/
Diwmmxt.S220 mov r0, #0 @ nothing to load
269 mov r0, #0 @ nothing to load
/linux-4.1.27/Documentation/video4linux/
DREADME.ir64 I know next to nothing about that through.
DREADME.pvrusb249 nothing to do with the API published by the driver to the outside
DZoran246 The adv717x, should be able to produce PAL N. But you find nothing PAL N
Dv4l2-framework.txt624 There is also a video_device_release_empty() function that does nothing
625 (is empty) and can be used if the struct is embedded and there is nothing
Dv4l2-controls.txt215 set, then it will just return and do nothing. This is also true for
/linux-4.1.27/drivers/net/wireless/p54/
DKconfig8 This module does nothing by itself - the USB/PCI/SPI front-ends
/linux-4.1.27/Documentation/scsi/
Dscsi.txt17 support. Without it you can do nothing with any of the other scsi drivers.
Dscsi_mid_low_api.txt445 * Returns nothing
479 * Returns nothing
520 * Returns nothing
535 * Returns nothing
632 * Returns nothing
688 * Returns nothing
701 * Returns nothing
1150 * Returns nothing
Daha152x.txt117 returned by the SCSI BIOS is a pure calculation and has nothing to
Dscsi-changer.txt24 media, nothing else.
DFlashPoint.txt90 overall problem of FlashPoint support for Linux users. It did nothing to
Dlibsas.txt314 Returns: -SAS_QUEUE_FULL, -ENOMEM, nothing was queued;
DLICENSE.qla4xxx192 signed it. However, nothing else grants you permission to modify or
DLICENSE.qla2xxx193 signed it. However, nothing else grants you permission to modify or
DChangeLog.megaraid251 so what's wrong about that? nothing, unless you
Dtmscsim.txt56 linux/drivers/scsi, you basically have to do nothing special to use this
Dst.txt318 MTNOP Do nothing except flush the buffers.
Dsym53c8xx_2.txt703 enabled when using Tekram cards. It does nothing useful for Tekram host
Dncr53c8xx.txt1476 enabled when using Tekram cards. It does nothing useful for Tekram host
DChangeLog.1992-1997836 if we have a "name" field, use it, else do nothing.
DChangeLog.lpfc736 to nothing more than the lpfc_nodelist pointer.
/linux-4.1.27/Documentation/laptops/
Dasus-laptop.txt160 Record its value, note any change. If nothing changes, try a broader range,
222 - 0x0 should do nothing
Dthinkpad-acpi.txt231 echo enable > /proc/acpi/ibm/hotkey -- does nothing
259 1: does nothing
929 embedded controller registers - e.g. make sure nothing else changes
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-wusb_cbaf31 has been authorized before and nothing further
/linux-4.1.27/drivers/scsi/
D53c700.scr163 ; Basically tell the selecting device that there's nothing here
269 ; Could be we have nothing more to transfer
D53c700_d.h_shipped199 ; Basically tell the selecting device that there's nothing here
473 ; Could be we have nothing more to transfer
/linux-4.1.27/sound/pci/ice1712/
Dwm8776.c96 static void snd_wm8776_set_agc(struct snd_wm8776 *wm, u16 agc, u16 nothing) in snd_wm8776_set_agc() argument
130 static void snd_wm8776_get_agc(struct snd_wm8776 *wm, u16 *mode, u16 *nothing) in snd_wm8776_get_agc() argument
/linux-4.1.27/Documentation/networking/
Dspider_net.txt156 is nothing to be done. In particular, there is the implicit assumption
162 Since its already full, the hardware can do nothing more, and thus has
166 and there can be no forward progress; the OS thinks there's nothing
Dgeneric-hdlc.txt84 It has nothing to do with clocks!
Dopenvswitch.txt45 kernel's, then nothing special is necessary.
50 does not understand IPv6), then again nothing special is
Dfib_trie.txt133 the child index until we find a match or the child index consists of nothing but
Ddccp.txt53 defined: the "simple" policy (DCCPQ_POLICY_SIMPLE), which does nothing special,
Dstmmac.txt348 that enable and disable the LPI mode when there is nothing to be
DLICENSE.qlge191 signed it. However, nothing else grants you permission to modify or
DLICENSE.qlcnic191 signed it. However, nothing else grants you permission to modify or
Dtimestamping.txt364 requested packets cannot be time stamped, then nothing should be
Dip-sysctl.txt203 buffer. Value 0 is special, it means that nothing is reserved.
1112 0 - (default): do nothing
1524 0 - (default): do nothing
Darcnet-hardware.txt217 There are also hubs for the TP topology. There is nothing difficult
357 ON ON Normal state - everything OK, nothing
1894 I know nothing about these. I just guess that J16&J17 are timeout
Dbonding.txt2575 nothing unusual, but examination of the BladeCenter cabinet would
/linux-4.1.27/Documentation/video4linux/bttv/
DPROBLEMS35 Since I do not know much (better make that almost nothing) about VGA card
/linux-4.1.27/drivers/parport/
Dparport_mfc3.c75 static inline int DPRINTK(void *nothing, ...) {return 0;} in DPRINTK() argument
/linux-4.1.27/Documentation/
Dmailbox.txt13 nothing prevents the remote f/w to also be Linux based and use the
Dcoccinelle.txt277 diff -u -p /home/user/linux/crypto/ctr.c /tmp/nothing
279 +++ /tmp/nothing
Drfkill.txt79 which compile to almost nothing.
Dpreempt-locking.txt78 call to preempt_enable. The preempt statements define to nothing if
Dflexible-arrays.txt105 This function works by scanning the array for pages containing nothing but
Deisa.txt174 EISA compliant mainboard (nothing appears on slot 0). Defaults to 0
Dcpu-hotplug.txt55 If nothing is specified,
262 notifier is called, when CPU_DEAD is called its expected there is nothing
Dkref.txt102 put needs no lock because nothing tries to get the data without
Dbus-virt-phys-mapping.txt138 there is really nothing you can do with such an address: it's not
DBUG-HUNTING56 This is how to track down a bug if you know nothing about kernel hacking.
Dxillybus.txt165 Note that the synchronization attribute has nothing to do with the possibility
242 host is up. In practice, nothing happens immediately in such a situation. But
Drobust-futex-ABI.txt179 current threads TID in the lower 29 bits, it does nothing with that
Dstable_api_nonsense.txt64 compile away to nothing for non-SMP builds.)
Dkernel-doc-nano-HOWTO.txt356 !C<filename> is replaced by nothing, but makes the tools check that
Dunshare.txt36 outside the confinement of all-or-nothing shared resources of legacy
Dsysrq.txt184 * I hit SysRq, but nothing seems to happen, what's wrong?
Doops-tracing.txt35 nothing. If the messages scroll off the top of the console, you
Dcachetlb.txt277 simply call memcpy/memset directly and do nothing more.
Datomic_ops.txt561 of the counter to zero. If it does not drop to zero, do nothing
Dedac.txt565 test_bits which in the current test driver does nothing but
Dpinctrl.txt202 stable value when nothing is driving the rail it is connected to, or when it's
1177 state and be done with it, there is nothing you need to do besides
Dparport-lowlevel.txt215 /* Failed; nothing we can do. */
Dmd.txt495 idle - nothing is happening
DDMA-API.txt310 aborting the request or even oopsing is better than doing nothing and
DHOWTO206 purpose, nothing is better than reading through it directly (most tricky
Dkmemcheck.txt690 as the first argument is legal (and will do nothing).
DSubmittingPatches464 the nature of your changes. While there is nothing mandatory about this, it
Dkernel-parameters.txt2091 is always true, so this option does nothing.
3071 prove do nothing more than free memory.
3281 0 The "airplane mode" button does nothing.
Dmemory-barriers.txt204 does nothing, but it is required for DEC Alpha. The ACCESS_ONCE()
1490 There is nothing to prevent the compiler from transforming
/linux-4.1.27/Documentation/frv/
Dkernel-ABI.txt199 determines that nothing needs doing. This is done simply with an
237 but this would do nothing as Z==1.
Dfeatures.txt127 Barring point (1), there is nothing to protect kernel data against
/linux-4.1.27/lib/
DKconfig.kgdb115 When KDB is active and a catastrophic error occurs, nothing extra
DKconfig.debug1001 kernel reports nothing.
/linux-4.1.27/Documentation/filesystems/
Dfiemap.txt50 nothing to prevent the file from changing between calls to FIEMAP.
119 extent will return nothing.
Ddebugfs.txt177 The dentry value can be NULL, in which case nothing will be removed.
Dramfs-rootfs-initramfs.txt300 require _truly_hideous_ command line arguments. But that says nothing
Dporting272 way by that code fixing will become trivial; until then nothing can be
Dpath-lookup.txt279 section on the grandparent, so we have nothing left to stand on. In that case,
Drelay.txt397 nothing but return 0.
Dxfs-delayed-logging-design.txt643 significant concern. Preventing lots of CPUs spinning doing nothing is the
644 main reason for choosing a sleeping lock even though nothing in either the
/linux-4.1.27/Documentation/i2c/
Dinstantiating-devices148 the OHCI adapter in question. It first tries at address 0x2c, if nothing
149 is found there it tries address 0x2d, and if still nothing is found, it
Dfault-codes88 means there's nothing listening at that address.
Dslave-interface69 there is nothing to process or return. Wakeup or initialization probably needs
/linux-4.1.27/Documentation/early-userspace/
Dbuffer-format.txt32 cpio_archive := cpio_file* + (<nothing> | cpio_trailer)
/linux-4.1.27/Documentation/hwmon/
Dadm1021102 If nothing happens when loading the adm1021 module, and you are certain
/linux-4.1.27/arch/nios2/
DKconfig128 chosen node and fall back to CMDLINE if nothing is passed.
/linux-4.1.27/Documentation/arm/Marvell/
DREADME192 * Due to their XScale origin, these SoCs have virtually nothing in
229 * Due to their XScale origin, these SoCs have virtually nothing in
/linux-4.1.27/security/selinux/
DKconfig63 kernel will start in permissive mode (log everything, deny nothing)
/linux-4.1.27/arch/m68k/ifpsp060/src/
Dfpsp.S3353 # fpsp_unsupp(), then we need to do nothing else for them here.
16382 rts # do nothing
16400 rts # no; do nothing
16418 beq.b fdbcc_ge_yes_done # no;go do nothing
16423 rts # do nothing
16441 rts # no; do nothing
16458 rts # do nothing
16476 rts # no; do nothing
16494 beq.b fdbcc_le_yes_done # no; go do nothing
16499 rts # do nothing
[all …]
Dpfpsp.S3352 # fpsp_unsupp(), then we need to do nothing else for them here.
/linux-4.1.27/drivers/net/wireless/b43/
DKconfig17 Note that this has nothing to do with the standard that your AccessPoint
/linux-4.1.27/Documentation/sound/oss/
DREADME.modules104 I'm afraid I know nothing about anything but my setup, being more of a
/linux-4.1.27/Documentation/dvb/
Dci.txt52 nothing much that can be done in order to make additional CI modules
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-decoder-api.txt11 This API call does nothing. It may be used to check if the firmware
Dfw-encoder-api.txt9 Does nothing. Can be used to check if the firmware is responding.
/linux-4.1.27/drivers/parisc/
DKconfig137 This has nothing to do with LED State support for A and E class.
/linux-4.1.27/Documentation/vm/
Dhwpoison.txt145 page-types -p `pidof init` --hwpoison # shall do nothing
Dunevictable-lru.txt342 statistics. If the page was already mlocked, mlock_vma_page() need do nothing
/linux-4.1.27/Documentation/blockdev/
Dramdisk.txt136 space on the RAM disk will compress to almost nothing.
/linux-4.1.27/sound/drivers/
DKconfig70 nothing, but emulates various mixer controls and PCM devices.
/linux-4.1.27/arch/arm/mm/
Dcache-v7.S99 ALT_UP( ret lr) @ LoUU is zero, so nothing to do
/linux-4.1.27/Documentation/locking/
Dspinlocks.txt140 handling in kernel/sched/core.c - nothing ever _changes_ a wait-queue from
Drt-mutex-design.txt475 is OK, since plist_del does nothing if the plist node is not on any
564 taken with the CMPXCHG and nothing else needs to be done.
739 owner field is set to NULL, the wait_lock is released and nothing more is
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Dmvebu-mbus.txt192 Yet in other words: there's nothing preventing us from setting a base address
/linux-4.1.27/arch/m68k/ifpsp060/
DTEST.DOC164 _real_XXXX() to do nothing except clear the exception
/linux-4.1.27/Documentation/input/
Djoystick-parport.txt267 However, there is nothing for free. To allow more sticks to be used at
474 Apart from making an interface, there is nothing difficult on using the
Datarikbd.txt416 Sets the ikbd to do nothing but monitor the serial command line, maintain the
429 Set the ikbd to do nothing but monitor the serial command line, maintain the
Delantech.txt129 default. Currently even turning it on will do nothing.
/linux-4.1.27/Documentation/power/
Dvideo.txt19 using vbetool later, or maybe nothing is necessary on particular
Ddevices.txt457 errors since there's nothing it can do about them other than printing them in
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt168 nothing happens in case of a kernel panic. If this value is set to "1"
599 stacked up next to each other so much that nothing else is
822 0: do nothing. This is the default behavior.
/linux-4.1.27/fs/reiserfs/
DREADME36 Finally, nothing in this license shall be interpreted to allow you to
/linux-4.1.27/scripts/
DKbuild.include74 # If no $(CC) found in PATH with listed prefixes return nothing
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt154 then the platform should re-enable IOs on the slot (or do nothing in
307 be recovered, there is nothing more that can be done; the platform
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt78 allocated during open(), so nothing is wasted when the camera is not in
/linux-4.1.27/arch/powerpc/
DKconfig.debug80 nothing will appear on the screen (xmon writes directly to the
/linux-4.1.27/drivers/block/
DKconfig246 Note that this loop device has nothing to do with the loopback
305 Note that this has nothing to do with the network file systems NFS
/linux-4.1.27/Documentation/filesystems/caching/
Dobject.txt202 write ops will be transparently discarded, and nothing recorded in the
Dfscache.txt104 netfs. The simplest cookie is just a NULL pointer - indicating nothing
/linux-4.1.27/Documentation/isdn/
DREADME.HiSax162 6 ELSA PCC/PCF cards io or nothing for autodetect (the iobase is
279 6 ELSA PCC/PCF cards pa=iobase or nothing for autodetect
DREADME537 If switched off, nothing happens in this case.
/linux-4.1.27/arch/unicore32/kernel/
Dentry.S418 mov r2, sp @ nothing stacked - regdump is at TOS
/linux-4.1.27/Documentation/target/
Dtcmu-design.txt346 /* Do nothing for PAD entries except update cmd_tail */
/linux-4.1.27/Documentation/block/
Dcfq-iosched.txt221 scheduling. For non-cgroup users nothing should change.
Dbiodoc.txt904 doesn't implement a function, the switch does nothing or some minimal house
/linux-4.1.27/Documentation/trace/
Dftrace-design.txt51 to see if it is set to ftrace_stub. If it is, there is nothing for you to do,
Dring-buffer-design.txt343 not pending or reserved), then there is nothing more to read.
Dftrace.txt534 This is the "trace nothing" tracer. To remove all
2610 not allocated |(do nothing)| alloc+swap |(do nothing)|
/linux-4.1.27/arch/m68k/fpsp040/
Dbindec.S266 fmovel #0,%FPSR |zero all of fpsr - nothing needed
Dres_func.S1354 orl #inf_mask,USER_FPSR(%a6) |if inf, nothing yet has set I
1362 orl #nan_mask,USER_FPSR(%a6) |if nan, nothing yet has set NaN
/linux-4.1.27/Documentation/thermal/
Dsysfs-api.txt154 will be created. when no_hwmon == true, nothing will be done.
/linux-4.1.27/Documentation/development-process/
D1.Intro204 lawyer, and nothing in this document can possibly be considered to be
D5.Posting270 - Send a copy to the relevant mailing list, or, if nothing else applies,
/linux-4.1.27/drivers/mtd/nand/
DKconfig208 approximately 5mA of power when there is nothing happening.
/linux-4.1.27/mm/
Dksm.c1713 static int ksm_scan_thread(void *nothing) in ksm_scan_thread() argument
/linux-4.1.27/Documentation/crypto/
Ddescore-readme.txt327 memory. Quick is included for programs that do nothing but DES,
/linux-4.1.27/arch/sparc/kernel/
Dentry.S1247 be 3f ! nothing to do
/linux-4.1.27/tools/usb/usbip/
DCOPYING181 signed it. However, nothing else grants you permission to modify or
/linux-4.1.27/drivers/staging/rtl8192e/
Dlicense184 it. However, nothing else grants you permission to modify or distribute
/linux-4.1.27/drivers/staging/rtl8192u/
Dcopying181 signed it. However, nothing else grants you permission to modify or
/linux-4.1.27/
DCOPYING197 signed it. However, nothing else grants you permission to modify or
/linux-4.1.27/Documentation/devicetree/
Dusage-model.txt77 structure that describes the hardware. There is nothing magical about
/linux-4.1.27/Documentation/arm64/
Darm-acpi.txt241 use the _DSD method for device properties and nothing else.
/linux-4.1.27/crypto/
DKconfig135 These are 'Null' algorithms, used by IPsec, which do nothing.
/linux-4.1.27/Documentation/m68k/
Dkernel-options.txt176 nothing happens.
/linux-4.1.27/Documentation/cgroups/
Dcpusets.txt213 cpusets every time any of them change to ensure nothing overlaps a
/linux-4.1.27/Documentation/x86/
Dboot.txt107 low, there is usually nothing the boot loader can do but to report an
/linux-4.1.27/arch/arm/
DKconfig.debug1141 is nothing connected to read from the DCC.
/linux-4.1.27/Documentation/kbuild/
Dmakefiles.txt568 then nothing is returned.
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex635 nothing wrong with this, but a good control of the `CD player' demands
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2668 After you run UML and it sits there doing nothing, you hit return at
4015 loop. UML uses the loop, since it has nothing resembling a TSC, and
/linux-4.1.27/init/
DKconfig1406 Almost nothing using the binary sysctl interface so if you are
/linux-4.1.27/arch/arm/crypto/
Dsha256-core.S_shipped32 @ code (meaning that latter performs sub-optimally, nothing was done
/linux-4.1.27/arch/x86/
DKconfig2184 this option does nothing.)
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt2320 are, it will do nothing and return an EBUSY error.