/linux-4.1.27/drivers/staging/media/mn88473/ |
D | TODO | 17 there is less lines. Those error checks are about the last thing to be added.
|
/linux-4.1.27/drivers/staging/media/mn88472/ |
D | TODO | 17 there is less lines. Those error checks are about the last thing to be added.
|
/linux-4.1.27/drivers/staging/media/bcm2048/ |
D | TODO | 5 The main thing you need to do is to implement all the controls using the
|
/linux-4.1.27/Documentation/ABI/obsolete/ |
D | sysfs-bus-usb | 31 same thing.
|
D | sysfs-driver-hid-roccat-koneplus | 10 Please use actual_profile, it does the same thing.
|
/linux-4.1.27/Documentation/ |
D | ManagementStyle | 74 thing you can backtrack on is a technical decision, and there 97 might be the wrong thing. You should always reserve the right to change 100 stupid thing. 114 thing you can do as a manager is not to instill confidence, but rather a 197 One thing to look out for is to realize that greatness in one area does 232 There's one thing people hate even more than being called "d*ckhead",
|
D | basic_profiling.txt | 6 <test> is the thing you're trying to measure.
|
D | stable_kernel_rules.txt | 8 - It must fix only one thing. 10 problem..." type thing).
|
D | circular-buffers.txt | 150 consumer that empties it. Only one thing should be filling a buffer at any one 151 time, and only one thing should be emptying a buffer at any one time, but the
|
D | bus-virt-phys-mapping.txt | 47 Now, that looks simple enough. However, when you look at the same thing from 61 where all the addresses actually point to the same thing. It's just seen
|
D | hwspinlock.txt | 178 * we took the lock, do our thing now, but do NOT sleep 213 * we took the lock, do our thing now, but do NOT sleep
|
D | DMA-ISA-LPC.txt | 55 thing. The reason for this is that the function isa_virt_to_phys()
|
D | preempt-locking.txt | 130 these are called from the spin_lock and read/write lock macros, the right thing
|
D | flexible-arrays.txt | 63 memory allocator would be a bad thing. That can be avoided by using
|
D | oops-tracing.txt | 77 The other thing to do is disassemble the "Code:" part of the bug report: 123 wonder how the NULL pointer got there, and if it's a valid thing to do
|
D | SubmittingDrivers | 115 often a good thing. If there is a stable working driver from
|
D | eisa.txt | 195 model is "the right thing"(tm).
|
D | printk-formats.txt | 243 n last components. %pD does the same thing for struct file.
|
D | crc32.txt | 4 and the whole thing (message+CRC) is a multiple of the given
|
D | sysfs-rules.txt | 38 There is no such thing like class-, bus-, physical devices,
|
D | email-clients.txt | 215 The easiest thing to do with Thunderbird and patches is to use an
|
D | CodingStyle | 349 Functions should be short and sweet, and do just one thing. They should 351 as we all know), and do one thing and do that well. 652 might look like a good thing, but it's confusing as hell when one reads the
|
D | svga.txt | 266 2.10 (11-Nov-96)- The whole thing made optional.
|
D | IPMI.txt | 468 that's not a simple thing and even the auto-tuning would need to be 712 ipmi_poweroff.poweroff_control=x will do the same thing on the kernel
|
D | bcache.txt | 119 invalidating the data at that lba in the cache (i.e. the same thing we do for
|
D | kobject.txt | 240 One important thing still missing from the discussion is what happens to a
|
D | dma-buf-sharing.txt | 369 subsystems shows that no driver seems to do any nefarious thing like syncing
|
D | atomic_ops.txt | 453 For one thing, this return value gets truncated to int in many code
|
D | edac.txt | 616 reset-counters writing ANY thing to this control will
|
D | md.txt | 312 is both (they come to the same thing).
|
D | SubmittingPatches | 648 patch. It will also be the only thing that people may quickly see
|
D | memory-barriers.txt | 1455 wrong thing for shared variables. For example, suppose you have 2308 and if any of these steps occur out of order, then the whole thing may
|
D | pinctrl.txt | 966 the same thing electrically speaking, but in this latter case the
|
/linux-4.1.27/Documentation/scsi/ |
D | hpsa.txt | 111 The above three ioctls all do exactly the same thing, which is to cause the driver 112 to rescan for new devices. This does exactly the same thing as writing to the
|
D | qlogicfas.txt | 25 thing to do is load the kernel without resetting the hardware, which
|
D | FlashPoint.txt | 78 vendors as the latest thing, and has been sold even on many of their high
|
D | libsas.txt | 204 can look like this (called last thing from probe())
|
D | tmscsim.txt | 89 Upgrading a SCSI driver is always a delicate thing to do. The 2.0 driver has
|
D | ChangeLog.sym53c8xx | 582 It is probably too early, but I wanted to complete the thing.
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | powersave.txt | 41 Try to turn it off when you experience such a thing too often.
|
D | OSS-Emulation.txt | 65 a totally different thing.)
|
D | HD-Audio.txt | 197 Thus, the first thing you can do for any brand-new, unsupported and
|
/linux-4.1.27/Documentation/sound/oss/ |
D | mwave | 9 OK, first thing - the IRQ problem IS a problem, whether the test is bypassed or 174 on why this second thing might be happening, I would be grateful.
|
D | CMI8330 | 10 The only thing you have to do is to compile the kernel sound
|
D | SoundPro | 34 it might be possible to do the same thing under Linux. You can try loading
|
D | README.OSS | 677 The first thing to do is to look at the major IC chips on the card. 688 There are many more cards in the world than listed above. The first thing to
|
/linux-4.1.27/Documentation/usb/ |
D | persist.txt | 27 "officially correct" thing to do. 79 same thing that happens whenever a USB device is reset.) If the 86 The same thing happens if the host controller is in the expected state
|
D | gadget_multi.txt | 52 The only thing to worry is that the gadget has to have a single 58 The other, trickier thing is making Windows install drivers for each
|
D | usb-serial.txt | 115 http://www.tekguru.co.uk/EM500/usbtonet.htm to achieve the same thing
|
D | power-management.txt | 184 power/control do essentially the same thing -- they both prevent the
|
/linux-4.1.27/Documentation/filesystems/ |
D | bfs.txt | 47 Just in case, you can verify that you have done the right thing by checking
|
D | hpfs.txt | 25 - there is a list of text extensions (I thing it's better to not convert 28 heuristic algorithm that I removed. I thing it's danger to let the 119 funny thing was that, when rebooted, PmShell tried to reopen this directory
|
D | tmpfs.txt | 14 you gain swapping and limit checking. Another similar thing is the RAM
|
D | debugfs.txt | 167 There is one important thing that all debugfs users must take into account:
|
D | romfs.txt | 138 Another thing to note is that romfs works on file headers and data
|
D | vfat.txt | 186 a get next directory entry approach. The only thing left that uses
|
D | seq_file.txt | 171 is a reasonable thing to do. The seq_file code will also avoid taking any
|
D | ramfs-rootfs-initramfs.txt | 173 The one thing you might need external cpio utilities installed for is creating
|
D | xfs-self-describing-metadata.txt | 137 thing that resets it is running xfs_repair on the filesystem. Further, by use of
|
D | sharedsubtree.txt | 233 to mean the same thing, throughout this document.
|
D | xfs-delayed-logging-design.txt | 90 The key thing to note about the asynchronous logging combined with the
|
/linux-4.1.27/Documentation/isdn/ |
D | README.syncppp | 5 You need one thing beside the isdn4linux package:
|
/linux-4.1.27/Documentation/sh/ |
D | new-machine.txt | 15 The first thing to note is the new directory structure. Under 2.4, most 88 The first thing to determine is whether the board you are adding will be 212 The first thing to do is to add an entry to arch/sh/Kconfig, under the
|
/linux-4.1.27/net/bluetooth/ |
D | Kconfig | 76 cases are run first thing at module load time. When the Bluetooth
|
/linux-4.1.27/drivers/hwmon/ |
D | f75375s.c | 658 #define show_fan(thing) \ argument 659 static ssize_t show_##thing(struct device *dev, struct device_attribute *attr, \ 664 return sprintf(buf, "%d\n", rpm_from_reg(data->thing[nr])); \
|
/linux-4.1.27/fs/proc/ |
D | Kconfig | 61 As it is generally a good thing, you should say Y here unless
|
/linux-4.1.27/arch/powerpc/boot/dts/ |
D | acadia.dts | 175 /* This thing is a bit weird. It has it's own UIC
|
D | ep405.dts | 218 /* That's all I know about IRQs on that thing ... */
|
/linux-4.1.27/Documentation/power/ |
D | s2ram.txt | 20 debugging - the thing that Chuck tried to disable. That's often the _only_
|
D | swsusp.txt | 112 Q: well, suspending a server is IMHO a really stupid thing, 177 "platform" is actually right thing to do where supported, but 297 inaccessible so they can't be stolen later on. The only thing that 404 safest thing is to unmount all filesystems on removable media (such USB,
|
D | swsusp-dmcrypt.txt | 27 The most important thing is that you set up dm-crypt in such
|
/linux-4.1.27/Documentation/i2c/ |
D | dev-interface | 21 first thing to do is "#include <linux/i2c-dev.h>". Please note that 33 Next thing, open the device file, as follows:
|
/linux-4.1.27/Documentation/powerpc/ |
D | ptrace.txt | 64 #define PPC_BREAKPOINT_CONDITION_EXACT 0x1 /* different name for the same thing as above */
|
D | pci_iov_resource_on_powernv.txt | 125 Then we do the same thing as with M32, using the bridge alignment
|
D | hvcs.txt | 451 (vt320) before you and leave the session logged in. The best thing to do
|
/linux-4.1.27/Documentation/dmaengine/ |
D | provider.txt | 74 The one last thing is that usually, slave devices won't issue DRQ by 109 The first thing you need to do in your driver is to allocate this 147 The next thing you need is to set which transaction types your device
|
/linux-4.1.27/Documentation/RCU/ |
D | rcu.txt | 48 thing at a time, why should I wait for a grace period?
|
D | whatisRCU.txt | 43 everything, feel free to read the whole thing -- but if you are really 181 section completes. For one thing, there might well be scheduling 182 delays. For another thing, many RCU implementations process 613 that the only thing that can block rcu_read_lock() is a synchronize_rcu().
|
D | listRCU.txt | 266 update-in-place performed by audit_upd_rule(). For one thing,
|
D | rcu_dereference.txt | 180 bugs more likely to happen. Which can be a good thing,
|
D | trace.txt | 75 a good thing in the surprisingly common case where NR_CPUS is
|
D | RTFP.txt | 9 The first thing resembling RCU was published in 1980, when Kung and Lehman 2128 State-based RCU. One key thing that this patch does is to
|
/linux-4.1.27/Documentation/development-process/ |
D | 7.AdvancedTopics | 114 thing happening; putting up a git tree with unreviewed or off-topic patches 166 by the patch as a whole is a good thing for the kernel or not. Yet others
|
D | 3.Early-stage | 166 One discouraging thing which can happen at this stage is not a hostile 178 idea. The best thing to do in this situation is to proceed, keeping the
|
D | 2.Process | 57 best thing to do is to wait for the next development cycle. (An occasional 329 directions. The whole thing would not work anywhere near as well as it
|
D | 6.Followthrough | 102 If a patch is considered to be a good thing to add to the kernel, and once
|
D | 5.Posting | 114 in the series enables the whole thing. This temptation should be
|
/linux-4.1.27/Documentation/hwmon/ |
D | ds1621 | 61 A second thing is that, during extensive testing, Tout showed a tolerance
|
D | w83781d | 388 One remarkable thing is that the fans would only have two or three
|
D | sysfs-interface | 714 hwmon sysfs attributes always contain numbers, so the first thing to do is to
|
/linux-4.1.27/Documentation/cgroups/ |
D | freezer-subsystem.txt | 122 This is the basic mechanism which should do the right thing for user space task
|
/linux-4.1.27/drivers/media/ |
D | Kconfig | 199 This is generally the right thing to do, except when there
|
/linux-4.1.27/Documentation/laptops/ |
D | sony-laptop.txt | 135 will work at all, or do the right thing. Although this hasn't
|
D | laptop-mode.txt | 218 from doing its thing.
|
D | thinkpad-acpi.txt | 452 The driver does the right thing,
|
/linux-4.1.27/arch/m68k/q40/ |
D | README | 115 One thing to keep in mind when hacking around the interrupt code is
|
/linux-4.1.27/Documentation/input/ |
D | gameport-programming.txt | 91 The only confusing thing here is the fuzz value. Best determined by
|
D | input-programming.txt | 218 that the thing is precise and always returns to exactly the center position
|
D | joystick-parport.txt | 87 And the last thing is the NES / SNES data wire. Only that isn't shared and
|
D | elantech.txt | 80 known whether the bits in the registers represent the same thing or might
|
/linux-4.1.27/Documentation/video4linux/ |
D | Zoran | 9 2. How do I get this damn thing to work 252 2. How do I get this damn thing to work 263 One thing to keep in mind is that this doesn't load zr36067.o itself yet. It
|
/linux-4.1.27/Documentation/i2c/busses/ |
D | i2c-i801 | 114 The first thing to try is the "i2c_ec" ACPI driver. It could be that the
|
/linux-4.1.27/Documentation/fb/ |
D | vesafb.txt | 129 * You'll get scrollback (the Shift-PgUp thing),
|
D | udlfb.txt | 77 to do its thing. The one extra feature they have is the ability to report
|
D | framebuffer.txt | 102 unaccelerated video hardware. The only thing that has to be built into
|
/linux-4.1.27/Documentation/acpi/apei/ |
D | einj.txt | 16 which is a different representation of the same thing.
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | knfsd-stats.txt | 88 thing. The ideal rate of change for this counter will be close
|
/linux-4.1.27/Documentation/networking/caif/ |
D | spi_porting.txt | 131 * in something similar to this. The only thing you need to
|
/linux-4.1.27/drivers/scsi/ |
D | 53c700.scr | 380 ; Data in and out do the same thing on resume, so pick one
|
D | 53c700_d.h_shipped | 785 ; Data in and out do the same thing on resume, so pick one
|
/linux-4.1.27/Documentation/security/ |
D | keys-request-key.txt | 194 Only if all these fail does the whole thing fail with the highest priority
|
D | Smack.txt | 401 label of the thing being accessed, and access is a string specifying the sort
|
/linux-4.1.27/fs/jffs2/ |
D | README.Locking | 81 ever actually implemented such a thing), it's now sufficient to use
|
/linux-4.1.27/ |
D | REPORTING-BUGS | 141 frustrating thing for maintainers is for someone to report a bug, and then
|
D | README | 326 isn't anyone listed there, then the second best thing is to mail
|
/linux-4.1.27/Documentation/watchdog/ |
D | watchdog-api.txt | 74 KEEPALIVE. This ioctl does exactly the same thing as a write to the
|
/linux-4.1.27/Documentation/locking/ |
D | rt-mutex-design.txt | 490 The important thing to remember is that the owner could not have 561 The first thing that is tried is the fast taking of the mutex. This is 583 slow path. The first thing that is done here is an atomic setting of 728 The first thing done in the slow unlock path is to take the wait_lock of the
|
D | lockdep-design.txt | 267 Of course, if you do run out of lock classes, the next thing to do is
|
/linux-4.1.27/Documentation/devicetree/ |
D | usage-model.txt | 76 The most important thing to understand is that the DT is simply a data 225 thing when using a DT.
|
D | booting-without-of.txt | 855 thing. It is recommended that if you add any "custom" property whose
|
/linux-4.1.27/drivers/usb/misc/ |
D | Kconfig | 145 the PCCARD. A rather pointless thing to do, but useful for testing.
|
/linux-4.1.27/Documentation/timers/ |
D | timekeeping.txt | 93 a different thing. The hardware driving clock events has to be able to
|
/linux-4.1.27/Documentation/hid/ |
D | uhid.txt | 47 The first thing you should do is sending an UHID_CREATE2 event. This will
|
/linux-4.1.27/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 1058 The first thing to do is bring the interface up: 1307 other ways of doing the same thing 1425 for it. The simplest thing to do is 1575 The first thing you need to do is run the daemon. Running it with no 1849 same file. That's the same thing as booting two physical machines 3397 writes to the idle thread's stack. That was the thing that happened 3777 stack and as the boot memory map. The last thing that the boot memory 3818 /usr/src/linux. If you do this, the first thing you need to do is 4135 needs a healthy tracing thread in order to work. The first thing to
|
/linux-4.1.27/Documentation/ide/ |
D | ChangeLog.ide-tape.1995-2002 | 27 * The one thing which needs to be done here is to
|
/linux-4.1.27/Documentation/block/ |
D | data-integrity.txt | 24 between adjacent nodes in the I/O path. The interesting thing about
|
D | biodoc.txt | 1032 always the right thing to do. Devices typically have their own queues, 1112 right thing to use is bio_endio(bio, uptodate) instead.
|
/linux-4.1.27/Documentation/mtd/ |
D | nand_ecc.txt | 397 Of course the same thing holds for rp4/5, rp6/7, rp8/9, rp10/11 and rp12/13. 677 But of course there is no such thing as a free lunch. The codesize almost
|
/linux-4.1.27/Documentation/s390/ |
D | 3270.txt | 220 the same thing from the input area, by typing "^C" and hitting ENTER.
|
D | Debugging390.txt | 187 The closest thing to this on traditional architectures is the interrupt 188 vector table. This is a good thing & does simplify some of the kernel coding 880 but are in primary space the easiest thing to do is to temporarily
|
/linux-4.1.27/drivers/net/ |
D | Kconfig | 66 thing often comes in handy, the default is Y. It won't enlarge your
|
/linux-4.1.27/Documentation/gpio/ |
D | consumer.txt | 142 The first thing a driver must do with a GPIO is setting its direction. If no
|
D | gpio-legacy.txt | 128 The first thing a system should do with a GPIO is allocate it, using
|
/linux-4.1.27/fs/befs/ |
D | ChangeLog | 296 in several respects. For one thing, it doesn't deal with indirect blocks
|
/linux-4.1.27/Documentation/arm/ |
D | cluster-pm-race-avoidance.txt | 98 therefore, a CPU can only be doing one thing at a single point in time.
|
/linux-4.1.27/Documentation/trace/ |
D | events.txt | 340 leaving that off in a '!' command will accomplish the same thing as
|
/linux-4.1.27/Documentation/networking/ |
D | phy.txt | 235 If you do need to write a PHY driver, the first thing to do is
|
D | arcnet-hardware.txt | 63 One thing that makes ARCnet cards difficult to program for, however, is the
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | cachefiles.txt | 47 to communication with the daemon. Only one thing may have this open at once,
|
/linux-4.1.27/Documentation/crypto/ |
D | descore-readme.txt | 171 one thing i did not want to do was write an enormous mess
|
/linux-4.1.27/arch/arm/crypto/ |
D | aesbs-core.S_shipped | 450 ite eq @ Thumb2 thing, sanity check in ARM 905 ite eq @ Thumb2 thing, samity check in ARM 2102 it ne @ Thumb2 thing, sanity check in ARM
|
D | sha256-core.S_shipped | 1829 ite eq @ Thumb2 thing, sanity check in ARM
|
/linux-4.1.27/Documentation/x86/ |
D | boot.txt | 292 Contains 0xAA55. This is the closest thing old Linux kernels have 725 is capable of examining its memory map. This is not the same thing
|
/linux-4.1.27/drivers/usb/host/ |
D | Kconfig | 655 the PCCARD. A rather pointless thing to do, but useful for testing.
|
/linux-4.1.27/Documentation/arm64/ |
D | arm-acpi.txt | 230 are always multiple ways to describe the same thing -- including device
|
/linux-4.1.27/drivers/ide/ |
D | Kconfig | 615 The nice thing about it is that you can mix Ultra/DMA/PIO devices
|
/linux-4.1.27/arch/mips/ |
D | Kconfig | 2734 # users to choose the right thing ...
|
/linux-4.1.27/init/ |
D | Kconfig | 226 exchange information. It is generally considered to be a good thing,
|