Home
last modified time | relevance | path

Searched refs:why (Results 1 – 172 of 172) sorted by relevance

/linux-4.1.27/include/linux/
Djbd.h276 #define J_EXPECT(expr, why...) J_ASSERT(expr) argument
277 #define J_EXPECT_BH(bh, expr, why...) J_ASSERT_BH(bh, expr) argument
278 #define J_EXPECT_JH(jh, expr, why...) J_ASSERT_JH(jh, expr) argument
280 #define __journal_expect(expr, why...) \
286 printk(KERN_ERR why "\n"); \
290 #define J_EXPECT(expr, why...) __journal_expect(expr, ## why)
291 #define J_EXPECT_BH(bh, expr, why...) __journal_expect(expr, ## why)
292 #define J_EXPECT_JH(jh, expr, why...) __journal_expect(expr, ## why)
Djbd2.h347 #define J_EXPECT(expr, why...) J_ASSERT(expr) argument
348 #define J_EXPECT_BH(bh, expr, why...) J_ASSERT_BH(bh, expr) argument
349 #define J_EXPECT_JH(jh, expr, why...) J_ASSERT_JH(jh, expr) argument
351 #define __journal_expect(expr, why...) \
358 printk(KERN_ERR why "\n"); \
362 #define J_EXPECT(expr, why...) __journal_expect(expr, ## why)
363 #define J_EXPECT_BH(bh, expr, why...) __journal_expect(expr, ## why)
364 #define J_EXPECT_JH(jh, expr, why...) __journal_expect(expr, ## why)
/linux-4.1.27/arch/mips/sgi-ip27/
DTODO1 1. Need to figure out why PCI writes to the IOC3 hang, and if it is okay
4 3. Need to figure out why address swaizzling is needed in inw/outw for
10 6. Investigate why things do not work without the setup_test() call
/linux-4.1.27/sound/core/
Dpcm_trace.h83 TP_PROTO(struct snd_pcm_substream *substream, const char *why),
84 TP_ARGS(substream, why),
97 __entry->reason = (why);
/linux-4.1.27/sound/oss/
Dhex2hex.c11 #define ABANDON(why) { fprintf(stderr, "%s\n", why); exit(1); } argument
/linux-4.1.27/fs/pstore/
Dplatform.c275 const char *why; in pstore_dump() local
282 why = get_reason_str(reason); in pstore_dump()
288 , in_nmi() ? "NMI" : why); in pstore_dump()
304 hsize = sprintf(dst, "%s#%d Part%u\n", why, in pstore_dump()
324 hsize = sprintf(dst, "%s#%d Part%u\n", why, oopscount, in pstore_dump()
/linux-4.1.27/kernel/
Dexit.c945 pid_t pid, uid_t uid, int why, int status) in wait_noreap_copyout() argument
959 retval = put_user((short)why, &infop->si_code); in wait_noreap_copyout()
990 int why; in wait_task_zombie() local
997 why = CLD_EXITED; in wait_task_zombie()
1000 why = (exit_code & 0x80) ? CLD_DUMPED : CLD_KILLED; in wait_task_zombie()
1003 return wait_noreap_copyout(wo, p, pid, uid, why, status); in wait_task_zombie()
1089 int why; in wait_task_zombie() local
1092 why = CLD_EXITED; in wait_task_zombie()
1095 why = (status & 0x80) ? CLD_DUMPED : CLD_KILLED; in wait_task_zombie()
1098 retval = put_user((short)why, &infop->si_code); in wait_task_zombie()
[all …]
Dsignal.c856 unsigned int why; in prepare_signal() local
879 why = 0; in prepare_signal()
881 why |= SIGNAL_CLD_CONTINUED; in prepare_signal()
883 why |= SIGNAL_CLD_STOPPED; in prepare_signal()
885 if (why) { in prepare_signal()
891 signal->flags = why | SIGNAL_STOP_CONTINUED; in prepare_signal()
1727 bool for_ptracer, int why) in do_notify_parent_cldstop() argument
1756 info.si_code = why; in do_notify_parent_cldstop()
1757 switch (why) { in do_notify_parent_cldstop()
1828 static void ptrace_stop(int exit_code, int why, int clear_code, siginfo_t *info) in ptrace_stop() argument
[all …]
/linux-4.1.27/arch/unicore32/kernel/
Dptrace.c115 asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) in syscall_trace() argument
129 regs->UCreg_ip = why; in syscall_trace()
Dentry.S138 why .req r22 @ Linux syscall (!= 0) label
457 mov why, #0
487 mov why, #0
548 mov r2, why @ 'syscall'
550 cmovne why, #0 @ prevent further restarts
634 2: mov why, #0 @ no longer a real syscall
673 mov why, #0 @ prevent syscall restart handling
/linux-4.1.27/arch/arm/kernel/
Dentry-common.S57 mov r2, why @ 'syscall'
208 mov why, #0 @ no longer a real syscall
299 mov why, #0 @ prevent syscall restart handling
305 mov why, #0 @ prevent syscall restart handling
Dentry-header.S400 why .req r8 @ Linux syscall (!= 0) label
/linux-4.1.27/scripts/
DKbuild.include208 echo ' $(call escsq,$($(quiet)cmd_$(1)))$(echo-why)';)
268 # why - tell why a a target got build
287 why = \
304 echo-why = $(call escsq, $(strip $(why)))
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-net-statistics154 See the driver for the exact reasons as to why the packets were
164 why the packets were dropped.
172 FIFO error. See the driver for the exact reasons as to why the
182 reasons as to why the packets were dropped.
Dsysfs-class-mic.txt75 entry provides the status on why the card OS was shutdown.
/linux-4.1.27/arch/cris/boot/rescue/
Drescue_v32.lds4 * but it doesn't do any harm on the other hand so why bother. */
/linux-4.1.27/Documentation/scheduler/
D00-INDEX12 - How and why the scheduler's nice levels are implemented.
Dsched-nice-design.txt99 task. (one will get 55% of the CPU, the other 45%.) That is why nice
Dcompletion.txt171 deliberately ignored a comment should probably explain why (e.g. see
/linux-4.1.27/Documentation/x86/
D00-INDEX12 - why and how Linux kernel uses exception tables on x86
Dexception-tables.txt281 That's it, mostly. If you look at our example, you might ask why
/linux-4.1.27/drivers/staging/lustre/lnet/klnds/socklnd/
Dsocklnd.h530 extern void ksocknal_close_conn_locked(ksock_conn_t *conn, int why);
534 __u32 ipaddr, int why);
535 extern int ksocknal_close_conn_and_siblings(ksock_conn_t *conn, int why);
Dsocklnd.c1678 ksocknal_close_peer_conns_locked(ksock_peer_t *peer, __u32 ipaddr, int why) in ksocknal_close_peer_conns_locked() argument
1691 ksocknal_close_conn_locked(conn, why); in ksocknal_close_peer_conns_locked()
1699 ksocknal_close_conn_and_siblings(ksock_conn_t *conn, int why) in ksocknal_close_conn_and_siblings() argument
1707 count = ksocknal_close_peer_conns_locked(peer, ipaddr, why); in ksocknal_close_conn_and_siblings()
/linux-4.1.27/Documentation/filesystems/
Dufs.txt14 type of ufs automatically. That's why user must specify type of
Dubifs.txt32 It should be quite obvious why UBIFS is very different to traditional
Dqnx6.txt132 If that structure shall fit for all allowed blocksizes, it is clear why there
Dromfs.txt149 understand why Avery wrote poems in the ARCnet docs to get some more
Dntfs.txt245 though untested, there is no reason why stripe sets, i.e. raid level 0, and
387 Even though untested, there is no reason why mirrors, i.e. raid level 1, and
Dgfs2-glocks.txt169 So why gather these statistics? There are several reasons
Dhpfs.txt72 why not use it for unix-specific info like file owner or access rights? This
DLocking486 components. And there are other reasons why the current interface is a mess...
Dxfs-delayed-logging-design.txt61 people should be able to see why the XFS metadata operations writes so much to
790 mount option. Fundamentally, there is no reason why the log manager would not
Dproc.txt749 clue as to how big an area you can safely allocate, or why a previous
/linux-4.1.27/fs/jffs2/
DLICENCE28 This exception does not invalidate any other reasons why a work based on
/linux-4.1.27/Documentation/thermal/
Dexynos_thermal_emulation29 change the value to updated one and just use last succeessful value repeatedly. That's why
/linux-4.1.27/Documentation/fb/
Dcmap_xfbdev.txt51 squares matching function. That's why the cmap entries can't be set to the left
Ddeferred_io.txt30 the final image rather than the intermediate stages which is why it's okay
Dsstfb.txt53 white rectangle. why? the function's name is self-explanatory:
/linux-4.1.27/Documentation/networking/
Dnetdev-FAQ.txt143 the upstream commit ID and why you think it should be a stable candidate.
147 explicitly indicate why it is a critical fix and exactly what users are
217 to why it happens, and then if necessary, explain why the fix proposed
Darcnet.txt35 If you think so, why not flame me in a quick little e-mail? Please also
257 don't know why the defaults on the Amiga didn't work; write to me if
518 significantly. In particular, they won't tell you why the card was not
Dopenvswitch.txt189 example, why 802.1Q support uses nested attributes. A TCP packet in
Dppp_generic.txt376 out why a PPP connection is failing.
Dcan.txt78 question arises, why we have started another project. Most existing
/linux-4.1.27/Documentation/video4linux/
DREADME.saa713462 - saa7130 - low-price chip, doesn't have mute, that is why all those
DZoran10 3. What mainboard should I use (or why doesn't my card work)
273 3. What mainboard should I use (or why doesn't my card work)
394 I woke up, and can't go to sleep again. I'll kill some time explaining why
430 6/8 of the specified buffers. (I'm not sure why. "Playing it safe" seem to be
DREADME.pvrusb256 functions, and there's no reason I see right now why it shouldn't be
/linux-4.1.27/Documentation/sound/oss/
Dmwave169 problem with the SB1.5 (CD sound) or SBPRO (Mixers) settings. No one knows why
174 on why this second thing might be happening, I would be grateful.
DREADME.OSS279 gives the 16 bit capability). The 8 bit only operation is the reason why
/linux-4.1.27/arch/cris/arch-v10/lib/
Dchecksum.S24 ;; this overhead is why we have a check above for breakeven length
Dchecksumcopy.S28 ;; this overhead is why we have a check above for breakeven length
/linux-4.1.27/drivers/block/drbd/
Ddrbd_int.h628 char *why; member
1136 char *why, enum bm_flag flags);
1139 char *why, enum bm_flag flags);
1142 char *why, enum bm_flag flags);
1383 extern void drbd_bm_lock(struct drbd_device *device, char *why, enum bm_flag flags);
Ddrbd_main.c3527 drbd_bm_lock(device, work->why, work->flags); in w_bitmap_io()
3540 work->why = NULL; in w_bitmap_io()
3564 char *why, enum bm_flag flags) in drbd_queue_bitmap_io() argument
3571 if (device->bm_io_work.why) in drbd_queue_bitmap_io()
3573 why, device->bm_io_work.why); in drbd_queue_bitmap_io()
3577 device->bm_io_work.why = why; in drbd_queue_bitmap_io()
3600 char *why, enum bm_flag flags) in drbd_bitmap_io() argument
3609 drbd_bm_lock(device, why, flags); in drbd_bitmap_io()
Ddrbd_bitmap.c129 void drbd_bm_lock(struct drbd_device *device, char *why, enum bm_flag flags) in drbd_bm_lock() argument
144 why, b->bm_why ?: "?", in drbd_bm_lock()
152 b->bm_why = why; in drbd_bm_lock()
Ddrbd_state.c1230 char *why, enum bm_flag flags) in drbd_bitmap_io_from_worker() argument
1239 drbd_bm_lock(device, why, flags); in drbd_bitmap_io_from_worker()
/linux-4.1.27/Documentation/
DSAK.txt40 know why.
DSubmitChecklist96 source code that explains the logic of what they are doing and why.
Dvolatile-considered-harmful.txt9 kernel code is almost never correct; this document describes why.
DHOWTO23 explain some of the reasons why the community works like it does.
435 clear and concise reasoning as to why those changes should not be made.
562 the Linux community know why they should add this change. New features
573 - why the change is necessary
Dstable_kernel_rules.txt52 why you think it should be applied, and what kernel version you wish it to
Dpi-futex.txt19 Priority Inheritance - why?
DManagementStyle223 Taking the blame is also why you get to be manager in the first place.
266 you're incompetent, the obvious question becomes one of why do it in the
Dbus-virt-phys-mapping.txt119 So why do we care about the physical address at all? We do need the physical
Dcrc32.txt8 is used by a lot of hardware implementations, and is why so many
Dstable_api_nonsense.txt6 This is being written to try to explain why Linux does not have a binary
Dunaligned-memory-access.txt6 unaligned accesses, why you need to write code that doesn't cause them,
DCodingStyle311 but if there is a clear reason for why it under certain circumstances
398 Choose label names which say what the goto does or why the goto exists. An
543 has, which is why you need to give it a few command line options.
Dthis_cpu_ops.txt215 so is expensive. If there are other reasons why the scheduler cannot
Dunshare.txt5 provides an overview of the feature, why it is needed, how it can
Doops-tracing.txt127 some small amount of concentration, you're right. Which is why I will
Drpmsg.txt185 a very good reason why not to always use RPMSG_ADDR_ANY here).
D00-INDEX423 - info on why the kernel does not have a stable in-kernel api or abi.
Dkprobes.txt97 that unexpectedly modifies that portion of the stack. This is why
DDMA-API-HOWTO.txt210 exactly why.
DSubmittingPatches655 as why the patch might be necessary. It is challenging to be both
Dmemory-barriers.txt1414 is why compilers reload variables. Doing so is perfectly safe for
/linux-4.1.27/Documentation/trace/
Devents-power.txt12 This document describes what each of the tracepoints is and why they
Devents-kmem.txt12 This document describes what each of the tracepoints is and why they
Dtracepoint-analysis.txt324 the card. Further investigation would be needed to determine why pixmaps
Dring-buffer-design.txt575 must spin, and this is why the reader cannot preempt the writer.
941 Now the writer can update the head page. This is also why the head page must
Dftrace.txt594 why a latency happened. Here is a typical trace.
/linux-4.1.27/fs/ocfs2/
Dfile.c572 enum ocfs2_alloc_restarted why = RESTART_NONE; in __ocfs2_extend_allocation() local
615 why, restart_func); in __ocfs2_extend_allocation()
644 &why); in __ocfs2_extend_allocation()
661 if (why != RESTART_NONE && clusters_to_add) { in __ocfs2_extend_allocation()
662 if (why == RESTART_META) { in __ocfs2_extend_allocation()
666 BUG_ON(why != RESTART_TRANS); in __ocfs2_extend_allocation()
Docfs2_trace.h1328 int why, int restart_func),
1329 TP_ARGS(ip_blkno, size, clusters, clusters_to_add, why, restart_func),
1335 __field(int, why)
1343 __entry->why = why;
1348 __entry->clusters_to_add, __entry->why, __entry->restart_func)
Dxattr.c720 enum ocfs2_alloc_restarted why; in ocfs2_xattr_extend_allocation() local
744 &why); in ocfs2_xattr_extend_allocation()
756 if (why != RESTART_NONE && clusters_to_add) { in ocfs2_xattr_extend_allocation()
761 BUG_ON(why == RESTART_META); in ocfs2_xattr_extend_allocation()
/linux-4.1.27/Documentation/m68k/
DREADME.buddha136 about 30ns to the clocks on the Zorro bus, that's why the
196 diskdrive would go crazy, that's why you shouldn't tune your
/linux-4.1.27/drivers/staging/lustre/lnet/selftest/
Drpc.c1323 srpc_abort_rpc(srpc_client_rpc_t *rpc, int why) in srpc_abort_rpc() argument
1325 LASSERT(why != 0); in srpc_abort_rpc()
1334 swi_state2str(rpc->crpc_wi.swi_state), why); in srpc_abort_rpc()
1337 rpc->crpc_status = why; in srpc_abort_rpc()
Dselftest.h434 void srpc_abort_rpc(srpc_client_rpc_t *rpc, int why);
/linux-4.1.27/Documentation/PCI/
DMSI-HOWTO.txt34 There are three reasons why using MSIs can give an advantage over
122 there are many reasons why the platform may not be able to provide the
278 there are many reasons why the platform may not be able to provide the
572 5.4. Finding why MSIs are disabled on a device
575 why MSIs may not be enabled for a given device. Your first step should
/linux-4.1.27/drivers/i2c/busses/
Di2c-pxa.c253 static void i2c_pxa_scream_blue_murder(struct pxa_i2c *i2c, const char *why) in i2c_pxa_scream_blue_murder() argument
256 printk(KERN_ERR "i2c: error: %s\n", why); in i2c_pxa_scream_blue_murder()
274 #define i2c_pxa_scream_blue_murder(i2c, why) do { } while (0) argument
/linux-4.1.27/Documentation/power/
Dfreezing-of-tasks.txt131 "RJW:> Why we freeze tasks at all or why we freeze kernel threads?
141 So in practice, the 'at all' may become a 'why freeze kernel threads?' and
171 may be undesirable. That's why kernel threads are not freezable by default.
Dswsusp.txt123 Q: Maybe I'm missing something, but why don't the regular I/O paths work?
162 Q: What is the freezing of tasks and why are we using it?
180 Q: I do not understand why you have such strong objections to idea of
419 2.6.15. Any idea for why that might happen or how can I speed it up?
Dsuspend-and-interrupts.txt16 there is no legitimate reason why any interrupts from suspended devices should
Dbasic-pm-debugging.txt41 To find out why hibernation fails on your system, you can use a special testing
/linux-4.1.27/Documentation/misc-devices/
Deeprom86 * Enable Writing. Again, no technical reason why not, but making it easy
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx-pinctrl.txt29 the pad setting value like pull-up on this pin. And that's why fsl,pins entry
/linux-4.1.27/Documentation/blockdev/
Dfloppy.txt34 prompt options coming last. That's why there are also options to
158 AMI ignored this, and used 5 for ED drives. That's why the floppy
/linux-4.1.27/fs/reiserfs/
DREADME111 why we should do what we do, or why innovation was possible in
/linux-4.1.27/Documentation/timers/
Dhrtimers.txt8 (kernel/timers.c), why do we need two timer subsystems? After a lot of
16 several reasons why such integration is hard/impossible:
Dtimekeeping.txt77 That is the reason why the clock source struct also contains a 'mask'
Dhighres.txt158 benefit. This is the reason why we currently disable high resolution and
/linux-4.1.27/Documentation/hwmon/
Dsis5595104 Some chips refuse to be enabled. We don't know why.
Dsubmitting-patches99 first. Either case, provide a detailed explanation why you need the
Dit87225 used to drive all fan outputs, which is why pwm2_freq and pwm3_freq are
Dabituguru-datasheet140 don't ask why this is the way it is.
/linux-4.1.27/Documentation/ABI/
DREADME38 why it is obsolete and when it can be expected to be removed.
/linux-4.1.27/Documentation/RCU/
Drcu.txt48 thing at a time, why should I wait for a grace period?
DUP.txt49 Quick Quiz #1: why is it -not- legal to invoke synchronize_rcu() in
Dchecklist.txt15 increasing write-side overhead, which is exactly why normal uses
38 earlier stores), and be prepared to explain why this added
/linux-4.1.27/Documentation/development-process/
D4.Coding323 understand the patch. Be sure that the changelog says *why* the patch is
359 be accompanied by a line explaining why the barrier is necessary. The
364 "cleanup" needs a comment saying why it is done the way it is. And so on.
379 accompanied by a description of what the change is and why it is
D6.Followthrough28 value and why you went to the trouble of writing it. But that value
190 If you disagree with the patch, send a polite response explaining why. If
D1.Intro17 encounter there. There are a great many reasons why kernel code should be
126 Some companies and developers occasionally wonder why they should bother
D7.AdvancedTopics93 of the reasons why development should be done in private branches (which
D5.Posting147 what the patch does and why it should be applied to the kernel.
D2.Process171 make those changes or justify why they should not be made. If your
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt121 value, which will be directly written in those bits, that is why,
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dentry.S314 ;; See copy_thread for the reason why register R9 is saved.
448 ;; is cleared by us however (when feeding the watchdog), which is why
/linux-4.1.27/Documentation/usb/
Dgadget_multi.txt95 Failing to comply may cause brain damage after wondering for hours why
Dusb-serial.txt418 why it is wise to cut down on the rate used is wise for large
/linux-4.1.27/drivers/video/fbdev/
Dsm501fb.c171 unsigned int why, size_t size, u32 smem_len) in sm501_alloc_mem() argument
178 switch (why) { in sm501_alloc_mem()
246 __func__, mem->sm_addr, mem->k_addr, why, size); in sm501_alloc_mem()
/linux-4.1.27/Documentation/vm/
Dhwpoison.txt25 * possibly violating some of their assumptions. This is why this code
Dtranshuge.txt83 be allocated instead of a 4k page for no good. This is why it's
Dunevictable-lru.txt46 descriptions below add value by provide the answer to "why does it do that?".
/linux-4.1.27/Documentation/rapidio/
Dsysfs.txt26 itself, this is why an endpoint with destID=1 is not shown in the list.
/linux-4.1.27/Documentation/connector/
Dconnector.txt141 so caller is warned that it must be prepared. That is why the struct
/linux-4.1.27/Documentation/input/
Diforce-protocol.txt4 from Immerse. That's why you should not trust what is written in this
Dinput.txt34 most of the existing input system, which is why it lives in
Djoystick-parport.txt142 Amstrad CPC, Sinclair ZX Spectrum and many other machines. That's why these
/linux-4.1.27/Documentation/locking/
Dspinlocks.txt127 (This is also the reason why the irq-versions of the spinlocks only need
Dlockdep-design.txt242 classes (see below discussion of reuse of lock classes for why).
Drt-mutex-design.txt10 It doesn't describe the reasons why rtmutex.c exists. For that please see
/linux-4.1.27/Documentation/powerpc/
Dtransactional_memory.txt173 These are defined in <asm/reg.h>, and distinguish different reasons why the
/linux-4.1.27/arch/frv/kernel/
Dentry.S878 # go as quickly as possible which is why some of this is
/linux-4.1.27/Documentation/arm/
DREADME45 explanation as to what the patch does and why it is needed.
Dcluster-pm-race-avoidance.txt8 The section "Rationale" explains what the algorithm is for and why it is
/linux-4.1.27/Documentation/sysctl/
Dvm.txt572 score, and name. This is helpful to determine why the OOM killer was
573 invoked, to identify the rogue task that caused it, and to determine why
699 why oom happens. You can get snapshot.
/linux-4.1.27/arch/cris/arch-v32/kernel/
Dentry.S347 ;; See copy_thread for the reason why register R9 is saved.
/linux-4.1.27/fs/affs/
DChanges200 affs use it on a 68k, they didn't notice. But why did
/linux-4.1.27/drivers/staging/lustre/lnet/klnds/o2iblnd/
Do2iblnd.h998 int kiblnd_close_peer_conns_locked (kib_peer_t *peer, int why);
Do2iblnd.c905 int kiblnd_close_peer_conns_locked(kib_peer_t *peer, int why) in kiblnd_close_peer_conns_locked() argument
917 conn->ibc_version, why); in kiblnd_close_peer_conns_locked()
919 kiblnd_close_conn_locked(conn, why); in kiblnd_close_peer_conns_locked()
Do2iblnd_cb.c2452 __u64 incarnation, int why, kib_connparams_t *cp) in kiblnd_reconnect() argument
2485 switch (why) { in kiblnd_reconnect()
/linux-4.1.27/Documentation/gpio/
Ddriver.txt152 keep track of usage inside of the gpiolib subsystem. This is why the API
/linux-4.1.27/drivers/media/usb/dvb-usb/
DKconfig214 old ttusb-driver - that's why the module is called dvb-usb-ttusb2.
/linux-4.1.27/Documentation/sound/alsa/
DCMIPCI.txt234 I don't know why..
/linux-4.1.27/Documentation/scsi/
DChangeLog.megaraid210 That, BTW, shows why cross-builds are useful-the only indication of
314 "I don't see why not ... it's your driver, you can publish whatever
Dscsi_eh.txt187 (*QUESTION* why is it needed? All operations will be blocked
Dscsi_mid_low_api.txt63 why this couldn't all be in one file; the header file is superfluous.] Some
1360 may get out of synchronization. This is why it is best for the LLD
DChangeLog.1992-1997591 did this and why was it important? 64 bit machines?
703 added these and why????
DChangeLog.sym53c8xx482 was in fact misplaced. BTW, this may explain why broken PCI
/linux-4.1.27/Documentation/ide/
Dide.txt234 controller, which is why an "IDE interface card" is not a "controller card".
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-kernel-api.txt134 Not all watchdog timer hardware supports the same functionality. That's why
/linux-4.1.27/Documentation/mtd/
Dnand_ecc.txt268 every modern microprocessor supports 32 bit operations, so why not try
396 rp14). That is why some places refer to inverse parity.
/linux-4.1.27/Documentation/laptops/
Dlaptop-mode.txt105 all block dirtyings done to files. This makes it possible to debug why a disk
207 * Drew Scott Daniels observed: "I don't know why, but when I decrease the number
/linux-4.1.27/Documentation/nfc/
Dnfc-hci.txt35 support proprietary gates. This is the reason why the driver will pass a list
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dhub.fuc96 // may find out if/why we need to handle these if so..
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt34 is why most if not all of the DMA controllers can adjust this, using a
/linux-4.1.27/Documentation/cgroups/
Dmemory.txt227 * why 'memory+swap' rather than swap.
808 explaining why would you need them.)
Dcgroups.txt660 is the reason why user defined extended attributes are not supported, since
Dcpusets.txt453 This mismatch is why there is not a simple one-to-one relation
/linux-4.1.27/scripts/genksyms/
Dparse.tab.c_shipped2212 user semantic actions for why this is necessary. */
2371 user semantic actions for why this is necessary. */
/linux-4.1.27/Documentation/crypto/
Ddescore-readme.txt88 it's a bit weak on common low-level optimizations which is why
/linux-4.1.27/
DREADME350 important: it tells something about why the kernel dumped code (in
/linux-4.1.27/scripts/kconfig/
Dzconf.tab.c_shipped2101 user semantic actions for why this is necessary. */
2260 user semantic actions for why this is necessary. */
/linux-4.1.27/scripts/dtc/
Ddtc-parser.tab.c_shipped2114 user semantic actions for why this is necessary. */
2275 user semantic actions for why this is necessary. */
/linux-4.1.27/Documentation/arm64/
Darm-acpi.txt29 useful to understand why ACPI is being used. Several technologies already
/linux-4.1.27/Documentation/spi/
Dspi-summary122 clock level when its select line goes active. That's why many devices
/linux-4.1.27/Documentation/kbuild/
Dmakefiles.txt562 explaining to the user why it stops.
/linux-4.1.27/Documentation/block/
Dbiodoc.txt322 <JENS: I dont understand the above, why is end_that_request_first() not
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq1572 * shouldn't hurt, but why do it twice...
Daic79xx.seq1044 * shouldn't hurt, but why do it twice...
/linux-4.1.27/lib/
DKconfig.debug237 mail to the linux kernel mailing list mentioning the symbol and why
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt3003 application code why KVM_RUN has returned. Allowable values for this
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt4025 why. See ``UML on 2G/2G hosts'' for the details on getting UML to
/linux-4.1.27/arch/m68k/ifpsp060/src/
Dfpsp.S4176 # often so that's why it gets lower priority.