| /linux-4.1.27/arch/mn10300/unit-asb2303/include/unit/ |
| D | timex.h | 47 # error You lose.
|
| /linux-4.1.27/arch/mn10300/unit-asb2305/include/unit/ |
| D | timex.h | 47 # error You lose.
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio-omap.txt | 27 so will never lose its logic state.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ocfs2.txt | 69 This means that if you lose your power, you will lose
|
| D | ext3.txt | 53 This means that if you lose your power, you will lose
|
| D | affs.txt | 30 gain above 4K seems not really worth the price, so you don't lose too
|
| D | ext4.txt | 175 This means that if you lose your power, you will lose
|
| D | relay.txt | 270 idea - you're guaranteed to either overwrite data or lose events
|
| /linux-4.1.27/Documentation/vm/ |
| D | soft-dirty.txt | 32 there is still a scenario when we can lose soft dirty bits -- a task
|
| D | transhuge.txt | 92 risk to lose memory by using hugepages, should use
|
| /linux-4.1.27/Documentation/power/ |
| D | swsusp.txt | 22 * they won't be accessible after resume and you may lose data, as though
346 anything, not even read-only mount, or you are going to lose your
383 I suspend to disk, I can lose data unless the filesystem has been mounted
386 A: That's right ... if you disconnect that device, you may lose data.
387 In fact, even with "-o sync" you can lose data if your programs have
|
| D | states.txt | 74 and put into low-power states. In many cases, all peripheral buses lose power
|
| /linux-4.1.27/drivers/usb/core/ |
| D | Kconfig | 25 devices that lose power get reenumerated as if they had been
|
| /linux-4.1.27/Documentation/s390/ |
| D | DASD | 62 the partition /dev/dd?1 instead of the whole volume. You only lose 3kB
|
| /linux-4.1.27/Documentation/input/ |
| D | joystick-api.txt | 107 is much safer since it can't lose sync with the driver. As you would
169 If time between reads is enough to fill the queue and lose an event,
|
| D | iforce-protocol.txt | 183 QUERY = 43 ('C')lose
|
| /linux-4.1.27/drivers/mmc/host/ |
| D | davinci_mmc.c | 787 bool lose = true; in mmc_davinci_set_ios() local
796 lose = false; in mmc_davinci_set_ios()
801 if (lose) in mmc_davinci_set_ios()
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | w83793 | 20 This parameter is not recommended, it will lose motherboard specific
|
| /linux-4.1.27/Documentation/frv/ |
| D | gdbstub.txt | 24 that the clock will lose time since it is implemented in software.
|
| /linux-4.1.27/Documentation/laptops/ |
| D | laptop-mode.txt | 55 so that you won't lose any data at the end of your battery life.
124 comfortable with. Worst case, it's possible that you could lose this
238 # comfortable with. Worst case, it's possible that you could lose this
353 # comfortable with. Worst case, it's possible that you could lose this
|
| /linux-4.1.27/Documentation/i2c/ |
| D | fault-codes | 39 Returned by I2C adapters when they lose arbitration in master
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | statistics.txt | 136 statistics does not want to lose any statistics (those updated
|
| D | cache.txt | 130 cache. If power is lost you may lose some recent writes. The metadata
|
| D | thin-provisioning.txt | 129 a volatile write cache. If power is lost you may lose some recent
|
| /linux-4.1.27/arch/m68k/q40/ |
| D | README | 19 When something blocks interrupts (HD) it will lose some of them, so far
|
| /linux-4.1.27/arch/frv/mm/ |
| D | tlb-miss.S | 175 # - IAMPR1 has no WP bit, and we mustn't lose WP information
|
| /linux-4.1.27/Documentation/fb/ |
| D | sstfb.txt | 141 patterns at the border of your windows (the pixels lose the lowest
|
| /linux-4.1.27/Documentation/trace/ |
| D | mmiotrace.txt | 74 Check that mmiotrace did not lose events due to a buffer filling up. Either
|
| D | ring-buffer-design.txt | 57 will stop writing to the buffer. This will lose most recent events.
61 overwrite the older data. This will lose the oldest events.
|
| /linux-4.1.27/net/netfilter/ipvs/ |
| D | Kconfig | 57 is 4096. Don't input the number too small, otherwise you will lose
|
| /linux-4.1.27/Documentation/ |
| D | kernel-doc-nano-HOWTO.txt | 105 descriptions won't work so well; derived documentation will lose
|
| D | bcache.txt | 140 maturity, but simply because in writeback mode you'll lose data if something
|
| D | parport-lowlevel.txt | 465 kfree (dev->private); /* before we lose the pointer */
|
| D | kmemcheck.txt | 650 particular field in a struct, for example, we will now lose the
|
| /linux-4.1.27/Documentation/networking/ |
| D | openvswitch.txt | 30 and existing protocols lose their prominence. For the Open vSwitch
|
| /linux-4.1.27/Documentation/block/ |
| D | cfq-iosched.txt | 273 and notice how a workload can lose its disk share and suffer due to
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 6.Followthrough | 174 development community remembers developers who lose interest in their code
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 140 SW. We lose a bit of effectiveness of EEH in that case, but that's
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 428 This means it may lose signals or ptrace events for example, and affects what
|
| /linux-4.1.27/drivers/char/ |
| D | Kconfig | 133 but it'll lose the kernel messages.
|
| /linux-4.1.27/Documentation/mtd/ |
| D | nand_ecc.txt | 563 million iterations in order not to lose too much accuracy. This one
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 299 function, we would lose the section information and thus
305 lose valueble information about where the mismatch was
|
| /linux-4.1.27/Documentation/usb/ |
| D | power-management.txt | 558 a charging application. In any event a logically off port will lose
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 454 * configurations, the SCB DMA engine may lose its place
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.lpfc | 480 test unit ready's, etc. This was causing us to lose
|