Home
last modified time | relevance | path

Searched refs:thing (Results 1 – 148 of 148) sorted by relevance

/linux-4.1.27/drivers/staging/media/mn88473/
DTODO17 there is less lines. Those error checks are about the last thing to be added.
/linux-4.1.27/drivers/staging/media/mn88472/
DTODO17 there is less lines. Those error checks are about the last thing to be added.
/linux-4.1.27/drivers/staging/media/bcm2048/
DTODO5 The main thing you need to do is to implement all the controls using the
/linux-4.1.27/Documentation/ABI/obsolete/
Dsysfs-bus-usb31 same thing.
Dsysfs-driver-hid-roccat-koneplus10 Please use actual_profile, it does the same thing.
/linux-4.1.27/Documentation/
DManagementStyle74 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",
Dbasic_profiling.txt6 <test> is the thing you're trying to measure.
Dstable_kernel_rules.txt8 - It must fix only one thing.
10 problem..." type thing).
Dcircular-buffers.txt150 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
Dbus-virt-phys-mapping.txt47 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
Dhwspinlock.txt178 * 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
DDMA-ISA-LPC.txt55 thing. The reason for this is that the function isa_virt_to_phys()
Dpreempt-locking.txt130 these are called from the spin_lock and read/write lock macros, the right thing
Dflexible-arrays.txt63 memory allocator would be a bad thing. That can be avoided by using
Doops-tracing.txt77 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
DSubmittingDrivers115 often a good thing. If there is a stable working driver from
Deisa.txt195 model is "the right thing"(tm).
Dprintk-formats.txt243 n last components. %pD does the same thing for struct file.
Dcrc32.txt4 and the whole thing (message+CRC) is a multiple of the given
Dsysfs-rules.txt38 There is no such thing like class-, bus-, physical devices,
Demail-clients.txt215 The easiest thing to do with Thunderbird and patches is to use an
DCodingStyle349 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
Dsvga.txt266 2.10 (11-Nov-96)- The whole thing made optional.
DIPMI.txt468 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
Dbcache.txt119 invalidating the data at that lba in the cache (i.e. the same thing we do for
Dkobject.txt240 One important thing still missing from the discussion is what happens to a
Ddma-buf-sharing.txt369 subsystems shows that no driver seems to do any nefarious thing like syncing
Datomic_ops.txt453 For one thing, this return value gets truncated to int in many code
Dedac.txt616 reset-counters writing ANY thing to this control will
Dmd.txt312 is both (they come to the same thing).
DSubmittingPatches648 patch. It will also be the only thing that people may quickly see
Dmemory-barriers.txt1455 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
Dpinctrl.txt966 the same thing electrically speaking, but in this latter case the
/linux-4.1.27/Documentation/scsi/
Dhpsa.txt111 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
Dqlogicfas.txt25 thing to do is load the kernel without resetting the hardware, which
DFlashPoint.txt78 vendors as the latest thing, and has been sold even on many of their high
Dlibsas.txt204 can look like this (called last thing from probe())
Dtmscsim.txt89 Upgrading a SCSI driver is always a delicate thing to do. The 2.0 driver has
DChangeLog.sym53c8xx582 It is probably too early, but I wanted to complete the thing.
/linux-4.1.27/Documentation/sound/alsa/
Dpowersave.txt41 Try to turn it off when you experience such a thing too often.
DOSS-Emulation.txt65 a totally different thing.)
DHD-Audio.txt197 Thus, the first thing you can do for any brand-new, unsupported and
/linux-4.1.27/Documentation/sound/oss/
Dmwave9 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.
DCMI833010 The only thing you have to do is to compile the kernel sound
DSoundPro34 it might be possible to do the same thing under Linux. You can try loading
DREADME.OSS677 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/
Dpersist.txt27 "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
Dgadget_multi.txt52 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
Dusb-serial.txt115 http://www.tekguru.co.uk/EM500/usbtonet.htm to achieve the same thing
Dpower-management.txt184 power/control do essentially the same thing -- they both prevent the
/linux-4.1.27/Documentation/filesystems/
Dbfs.txt47 Just in case, you can verify that you have done the right thing by checking
Dhpfs.txt25 - 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
Dtmpfs.txt14 you gain swapping and limit checking. Another similar thing is the RAM
Ddebugfs.txt167 There is one important thing that all debugfs users must take into account:
Dromfs.txt138 Another thing to note is that romfs works on file headers and data
Dvfat.txt186 a get next directory entry approach. The only thing left that uses
Dseq_file.txt171 is a reasonable thing to do. The seq_file code will also avoid taking any
Dramfs-rootfs-initramfs.txt173 The one thing you might need external cpio utilities installed for is creating
Dxfs-self-describing-metadata.txt137 thing that resets it is running xfs_repair on the filesystem. Further, by use of
Dsharedsubtree.txt233 to mean the same thing, throughout this document.
Dxfs-delayed-logging-design.txt90 The key thing to note about the asynchronous logging combined with the
/linux-4.1.27/Documentation/isdn/
DREADME.syncppp5 You need one thing beside the isdn4linux package:
/linux-4.1.27/Documentation/sh/
Dnew-machine.txt15 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/
DKconfig76 cases are run first thing at module load time. When the Bluetooth
/linux-4.1.27/drivers/hwmon/
Df75375s.c658 #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/
DKconfig61 As it is generally a good thing, you should say Y here unless
/linux-4.1.27/arch/powerpc/boot/dts/
Dacadia.dts175 /* This thing is a bit weird. It has it's own UIC
Dep405.dts218 /* That's all I know about IRQs on that thing ... */
/linux-4.1.27/Documentation/power/
Ds2ram.txt20 debugging - the thing that Chuck tried to disable. That's often the _only_
Dswsusp.txt112 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,
Dswsusp-dmcrypt.txt27 The most important thing is that you set up dm-crypt in such
/linux-4.1.27/Documentation/i2c/
Ddev-interface21 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/
Dptrace.txt64 #define PPC_BREAKPOINT_CONDITION_EXACT 0x1 /* different name for the same thing as above */
Dpci_iov_resource_on_powernv.txt125 Then we do the same thing as with M32, using the bridge alignment
Dhvcs.txt451 (vt320) before you and leave the session logged in. The best thing to do
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt74 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/
Drcu.txt48 thing at a time, why should I wait for a grace period?
DwhatisRCU.txt43 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().
DlistRCU.txt266 update-in-place performed by audit_upd_rule(). For one thing,
Drcu_dereference.txt180 bugs more likely to happen. Which can be a good thing,
Dtrace.txt75 a good thing in the surprisingly common case where NR_CPUS is
DRTFP.txt9 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/
D7.AdvancedTopics114 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
D3.Early-stage166 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
D2.Process57 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
D6.Followthrough102 If a patch is considered to be a good thing to add to the kernel, and once
D5.Posting114 in the series enables the whole thing. This temptation should be
/linux-4.1.27/Documentation/hwmon/
Dds162161 A second thing is that, during extensive testing, Tout showed a tolerance
Dw83781d388 One remarkable thing is that the fans would only have two or three
Dsysfs-interface714 hwmon sysfs attributes always contain numbers, so the first thing to do is to
/linux-4.1.27/Documentation/cgroups/
Dfreezer-subsystem.txt122 This is the basic mechanism which should do the right thing for user space task
/linux-4.1.27/drivers/media/
DKconfig199 This is generally the right thing to do, except when there
/linux-4.1.27/Documentation/laptops/
Dsony-laptop.txt135 will work at all, or do the right thing. Although this hasn't
Dlaptop-mode.txt218 from doing its thing.
Dthinkpad-acpi.txt452 The driver does the right thing,
/linux-4.1.27/arch/m68k/q40/
DREADME115 One thing to keep in mind when hacking around the interrupt code is
/linux-4.1.27/Documentation/input/
Dgameport-programming.txt91 The only confusing thing here is the fuzz value. Best determined by
Dinput-programming.txt218 that the thing is precise and always returns to exactly the center position
Djoystick-parport.txt87 And the last thing is the NES / SNES data wire. Only that isn't shared and
Delantech.txt80 known whether the bits in the registers represent the same thing or might
/linux-4.1.27/Documentation/video4linux/
DZoran9 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/
Di2c-i801114 The first thing to try is the "i2c_ec" ACPI driver. It could be that the
/linux-4.1.27/Documentation/fb/
Dvesafb.txt129 * You'll get scrollback (the Shift-PgUp thing),
Dudlfb.txt77 to do its thing. The one extra feature they have is the ability to report
Dframebuffer.txt102 unaccelerated video hardware. The only thing that has to be built into
/linux-4.1.27/Documentation/acpi/apei/
Deinj.txt16 which is a different representation of the same thing.
/linux-4.1.27/Documentation/filesystems/nfs/
Dknfsd-stats.txt88 thing. The ideal rate of change for this counter will be close
/linux-4.1.27/Documentation/networking/caif/
Dspi_porting.txt131 * in something similar to this. The only thing you need to
/linux-4.1.27/drivers/scsi/
D53c700.scr380 ; Data in and out do the same thing on resume, so pick one
D53c700_d.h_shipped785 ; Data in and out do the same thing on resume, so pick one
/linux-4.1.27/Documentation/security/
Dkeys-request-key.txt194 Only if all these fail does the whole thing fail with the highest priority
DSmack.txt401 label of the thing being accessed, and access is a string specifying the sort
/linux-4.1.27/fs/jffs2/
DREADME.Locking81 ever actually implemented such a thing), it's now sufficient to use
/linux-4.1.27/
DREPORTING-BUGS141 frustrating thing for maintainers is for someone to report a bug, and then
DREADME326 isn't anyone listed there, then the second best thing is to mail
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-api.txt74 KEEPALIVE. This ioctl does exactly the same thing as a write to the
/linux-4.1.27/Documentation/locking/
Drt-mutex-design.txt490 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
Dlockdep-design.txt267 Of course, if you do run out of lock classes, the next thing to do is
/linux-4.1.27/Documentation/devicetree/
Dusage-model.txt76 The most important thing to understand is that the DT is simply a data
225 thing when using a DT.
Dbooting-without-of.txt855 thing. It is recommended that if you add any "custom" property whose
/linux-4.1.27/drivers/usb/misc/
DKconfig145 the PCCARD. A rather pointless thing to do, but useful for testing.
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt93 a different thing. The hardware driving clock events has to be able to
/linux-4.1.27/Documentation/hid/
Duhid.txt47 The first thing you should do is sending an UHID_CREATE2 event. This will
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1058 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/
DChangeLog.ide-tape.1995-200227 * The one thing which needs to be done here is to
/linux-4.1.27/Documentation/block/
Ddata-integrity.txt24 between adjacent nodes in the I/O path. The interesting thing about
Dbiodoc.txt1032 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/
Dnand_ecc.txt397 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/
D3270.txt220 the same thing from the input area, by typing "^C" and hitting ENTER.
DDebugging390.txt187 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/
DKconfig66 thing often comes in handy, the default is Y. It won't enlarge your
/linux-4.1.27/Documentation/gpio/
Dconsumer.txt142 The first thing a driver must do with a GPIO is setting its direction. If no
Dgpio-legacy.txt128 The first thing a system should do with a GPIO is allocate it, using
/linux-4.1.27/fs/befs/
DChangeLog296 in several respects. For one thing, it doesn't deal with indirect blocks
/linux-4.1.27/Documentation/arm/
Dcluster-pm-race-avoidance.txt98 therefore, a CPU can only be doing one thing at a single point in time.
/linux-4.1.27/Documentation/trace/
Devents.txt340 leaving that off in a '!' command will accomplish the same thing as
/linux-4.1.27/Documentation/networking/
Dphy.txt235 If you do need to write a PHY driver, the first thing to do is
Darcnet-hardware.txt63 One thing that makes ARCnet cards difficult to program for, however, is the
/linux-4.1.27/Documentation/filesystems/caching/
Dcachefiles.txt47 to communication with the daemon. Only one thing may have this open at once,
/linux-4.1.27/Documentation/crypto/
Ddescore-readme.txt171 one thing i did not want to do was write an enormous mess
/linux-4.1.27/arch/arm/crypto/
Daesbs-core.S_shipped450 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
Dsha256-core.S_shipped1829 ite eq @ Thumb2 thing, sanity check in ARM
/linux-4.1.27/Documentation/x86/
Dboot.txt292 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/
DKconfig655 the PCCARD. A rather pointless thing to do, but useful for testing.
/linux-4.1.27/Documentation/arm64/
Darm-acpi.txt230 are always multiple ways to describe the same thing -- including device
/linux-4.1.27/drivers/ide/
DKconfig615 The nice thing about it is that you can mix Ultra/DMA/PIO devices
/linux-4.1.27/arch/mips/
DKconfig2734 # users to choose the right thing ...
/linux-4.1.27/init/
DKconfig226 exchange information. It is generally considered to be a good thing,