Home
last modified time | relevance | path

Searched refs:who (Results 1 – 200 of 207) sorted by relevance

12

/linux-4.1.27/block/
Dioprio.c61 SYSCALL_DEFINE3(ioprio_set, int, which, int, who, int, ioprio) in SYSCALL_DEFINE3() argument
95 if (!who) in SYSCALL_DEFINE3()
98 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
103 if (!who) in SYSCALL_DEFINE3()
106 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
114 uid = make_kuid(current_user_ns(), who); in SYSCALL_DEFINE3()
117 if (!who) in SYSCALL_DEFINE3()
133 if (who) in SYSCALL_DEFINE3()
178 SYSCALL_DEFINE2(ioprio_get, int, which, int, who) in SYSCALL_DEFINE2() argument
190 if (!who) in SYSCALL_DEFINE2()
[all …]
/linux-4.1.27/arch/s390/kvm/
Dtrace-s390.h114 TP_PROTO(__u64 type, __u32 parm, __u64 parm64, int who),
115 TP_ARGS(type, parm, parm64, who),
121 __field(int, who)
128 __entry->who = who;
132 (__entry->who == 1) ? " (from kernel)" :
133 (__entry->who == 2) ? " (from user)" : "",
141 int who),
142 TP_ARGS(id, type, parm, parm64, who),
149 __field(int, who)
157 __entry->who = who;
[all …]
/linux-4.1.27/drivers/staging/lustre/lustre/obdclass/
Ddebug.c74 int block_debug_check(char *who, void *addr, int end, __u64 off, __u64 id) in block_debug_check() argument
85 who, id, off, *(__u64 *)addr, ne_off); in block_debug_check()
90 who, id, off, *(__u64 *)(addr + LPDS), id); in block_debug_check()
97 who, id, off, *(__u64 *)addr, ne_off); in block_debug_check()
102 who, id, off, *(__u64 *)(addr + LPDS), id); in block_debug_check()
/linux-4.1.27/kernel/
Dsys.c175 SYSCALL_DEFINE3(setpriority, int, which, int, who, int, niceval) in SYSCALL_DEFINE3() argument
198 if (who) in SYSCALL_DEFINE3()
199 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
206 if (who) in SYSCALL_DEFINE3()
207 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
215 uid = make_kuid(cred->user_ns, who); in SYSCALL_DEFINE3()
217 if (!who) in SYSCALL_DEFINE3()
245 SYSCALL_DEFINE2(getpriority, int, which, int, who) in SYSCALL_DEFINE2() argument
261 if (who) in SYSCALL_DEFINE2()
262 p = find_task_by_vpid(who); in SYSCALL_DEFINE2()
[all …]
/linux-4.1.27/Documentation/development-process/
D1.Intro6 accessible to those who are not intimately familiar with Linux kernel
70 those products attractive to Linux users. Embedded systems vendors, who
73 other software vendors who base their products on Linux have a clear
98 experience behind it. A developer who does not understand the kernel
99 community's ways (or, worse, who tries to flout or circumvent them) will
101 being helpful to those who are trying to learn, has little time for those
102 who will not listen or who do not care about the development process.
104 It is hoped that those who read this document will be able to avoid that
107 community is always in need of developers who will help to make the kernel
108 better; the following text should help you - or those who work for you -
[all …]
D5.Posting26 patches which are known to be half-baked, but those who do will come in
104 users who are engaging in the noble work of tracking down problems.
137 enough for a reader who sees it with no other context to figure out the
156 These include subsystem maintainers and reviewers who need to decide
160 chasing, users who want to know how the kernel has changed, and more. A
174 general, the more you can put yourself into the shoes of everybody who will
216 - Reported-by: names a user who reported a problem which is fixed by this
218 people who test our code and let us know when things do not work
254 When mailing patches, it is important to send copies to anybody who might
263 - Other developers who have been working in the same area - especially
[all …]
D3.Early-stage133 MAINTAINERS file may, in fact, not be the person who is actually acting in
134 that role currently. So, when there is doubt about who to contact, a
135 useful trick is to use git (and "git log" in particular) to see who is
136 currently active within the subsystem of interest. Look at who is writing
137 patches, and who, if anybody, is attaching Signed-off-by lines to those
138 patches. Those are the people who will be best placed to help with a new
148 command line, it will list the maintainers who should probably receive
152 who have no real interest in the code you are modifying.
D2.Process54 allowed, but such occasions are rare; developers who try to merge new
201 There is exactly one person who can merge patches into the mainline kernel
212 who has overall responsibility for the code within that subsystem. These
214 of the kernel they manage; they are the ones who will (usually) accept a
351 Among the kernel developers who do not use git, the most popular choice is
376 represent a potential hazard to developers, who risk getting buried under a
393 development community comes together as a whole; developers who avoid this
405 without changing the email subject line) and the people who are
419 questions. Some developers can get impatient with people who clearly
431 beginning developers to go wrong. Somebody who asks a networking-related
[all …]
D6.Followthrough36 people remember who wrote kernel code, but there is little lasting fame
37 for those who reviewed it. So reviewers can get grumpy, especially when
140 may be a new round of comments from developers who had not been aware of
143 though; you still need to be responsive to developers who have questions or
174 development community remembers developers who lose interest in their code
D8.Conclusion52 Congratulations to anybody who has made it through this long-winded
D7.AdvancedTopics25 fits into the kernel development process in particular. Developers who
155 developer who may well feel nervous about questioning code - in public -
D4.Coding93 programmers, who see it as a way to efficiently encode a great deal of
321 of the solution, the people who worked on the patch, any relevant
351 Anybody who reads through a significant amount of existing kernel code will
383 The other catch is that a developer who changes an internal API is
/linux-4.1.27/arch/s390/
DKconfig.debug16 Memory access is required for experts who want to debug the kernel.
27 who are working in architecture specific areas of the kernel.
DKconfig674 Everybody who wants to run Linux under VM != VM4.2 should select
699 Everybody who wants to run Linux under VM should select this
/linux-4.1.27/arch/x86/kernel/
De820.c161 void __init e820_print_map(char *who) in e820_print_map() argument
166 printk(KERN_INFO "%s: [mem %#018Lx-%#018Lx] ", who, in e820_print_map()
1029 char *who = "BIOS-e820"; in default_machine_specific_memory_setup() local
1050 who = "BIOS-88"; in default_machine_specific_memory_setup()
1053 who = "BIOS-e801"; in default_machine_specific_memory_setup()
1062 return who; in default_machine_specific_memory_setup()
1067 char *who; in setup_memory_map() local
1069 who = x86_init.resources.memory_setup(); in setup_memory_map()
1072 e820_print_map(who); in setup_memory_map()
/linux-4.1.27/Documentation/vm/
Dpage_owner.txt1 page owner: Tracking about who allocated each page
6 page owner is for the tracking about who allocated each page.
14 using it for analyzing who allocate each page is rather complex. We need
80 See the result about who allocated each page
Dactive_mm.txt77 because it slightly changes the interfaces to accommodate the alpha (who
Dhwpoison.txt61 This allows applications who can process memory errors in a gentle
Dhugetlbpage.txt310 Users who wish to use hugetlb memory via shared memory segment should be a
/linux-4.1.27/arch/ia64/kernel/
Dsys_ia64.c68 ia64_getpriority (int which, int who) in ia64_getpriority() argument
72 prio = sys_getpriority(which, who); in ia64_getpriority()
/linux-4.1.27/Documentation/block/
Dioprio.txt89 static inline int ioprio_set(int which, int who, int ioprio)
91 return syscall(__NR_ioprio_set, which, who, ioprio);
94 static inline int ioprio_get(int which, int who)
96 return syscall(__NR_ioprio_get, which, who);
/linux-4.1.27/include/linux/
Dresource.h9 int getrusage(struct task_struct *p, int who, struct rusage __user *ru);
Dsyscalls.h311 asmlinkage long sys_setpriority(int which, int who, int niceval);
312 asmlinkage long sys_getpriority(int which, int who);
654 asmlinkage long sys_getrusage(int who, struct rusage __user *ru);
721 asmlinkage long sys_ioprio_set(int which, int who, int ioprio);
722 asmlinkage long sys_ioprio_get(int which, int who);
Dcompat.h593 asmlinkage long compat_sys_getrusage(int who, struct compat_rusage __user *ru);
/linux-4.1.27/drivers/staging/lustre/lustre/include/
Dlustre_debug.h52 int block_debug_check(char *who, void *addr, int len, __u64 off, __u64 id);
/linux-4.1.27/Documentation/dvb/
Dreadme.txt39 is the who-is-who of DVB development.
DREADME.dvb-usb212 Jung from AVerMedia who kindly provided a special firmware to get the device
Davermedia.txt198 Here's my channels.conf file for anyone who's interested:
/linux-4.1.27/fs/nfsd/
Dacl.h52 __be32 nfs4_acl_write_who(struct xdr_stream *xdr, int who);
Dnfs4acl.c879 __be32 nfs4_acl_write_who(struct xdr_stream *xdr, int who) in nfs4_acl_write_who() argument
885 if (s2t_map[i].type != who) in nfs4_acl_write_who()
/linux-4.1.27/drivers/w1/slaves/
DKconfig88 as the one who is responsible for charging/discharging/monitoring
100 as the one who is responsible for charging/discharging/monitoring
112 as the one who is responsible for charging/discharging/monitoring
/linux-4.1.27/fs/
Dfcntl.c113 int who = arg; in f_setown() local
115 if (who < 0) { in f_setown()
117 who = -who; in f_setown()
120 pid = find_vpid(who); in f_setown()
DKconfig.binfmt115 who need to run binaries from that era.
/linux-4.1.27/Documentation/
DManagementStyle5 on who you ask) management style for the linux kernel. It's meant to
15 lead persons, not the people who do traditional management inside
105 This preemptive admission of incompetence might also make the people who
167 trust somebody who is so clearly hiding his true character.
186 Suck up to them, because they are the people who will make your job
214 guy who lost his whole 36GB porn-collection because of your incompetence
217 Then make the developer who really screwed up (if you can find him) know
220 importantly, he's also likely the person who can fix it. Because, let's
225 glory, because you're the one who gets to say "I screwed up". And if
252 without making it painful to the recipient, who just thinks you're being
DCodeOfConflict20 information on who is on the Technical Advisory Board and what their
DSecurityBugs10 who will help verify the bug report and develop and release a fix.
DSubmittingPatches8 For a person or company who wishes to submit a change to the Linux
268 source code revision history to see who those maintainers are. The
410 To improve tracking of who did what, especially with patches that can
437 person who certified (a), (b) or (c) and I have not modified
540 The Reported-by tag gives credit to people who find bugs and report them and it
577 technical issues. Any interested reviewer (who has done the work) can
681 The "from" line specifies who will be credited as the author of the
687 changelog, so should make sense to a competent reader who has long
691 especially useful for people who might be searching the commit logs
756 be a good way to find developers who can sign your key.
Dstable_api_nonsense.txt31 It's only the odd person who wants to write a kernel driver that needs
91 This is a much more "volatile" topic if you talk to people who try to
163 up by the person who did the kernel change in the first place. This
DHOWTO11 to the maintainer of this file, who is listed at the bottom of the
88 who are new to the kernel should start here.
271 This is the recommended branch for users who want the most recent stable
493 Most women who have worked in the Linux kernel and have expressed an
496 The language barrier can cause problems for some people who are not
596 Thanks to Paolo Ciarrocchi who allowed the "Development Process"
Dhw_random.txt72 However, for people who use mem=XX, BIOS e820 information is
Dvolatile-considered-harmful.txt97 additional scrutiny to the code. Developers who are tempted to use
Dstable_kernel_rules.txt131 - This is made up of a number of kernel developers who have volunteered for
DSubmittingDrivers122 tree. Anyone who tells you otherwise isn't telling the
Dapplying-patches.txt139 this is the case -- if so, then this is an error by the person who created
276 This is the recommended branch for users who want the most recent stable
316 This is a good branch to run for people who want to help out testing
Dunicode.txt170 not be normatively assigned, but it is recommended that people who
Dvgaarbiter.txt146 trying to lock different resources, only the first who tried succeeds.
Dkref.txt119 involved where the above may be legal) but someone else who doesn't
Dbus-virt-phys-mapping.txt183 didn't think straight when I wrote it originally. People who have to
DBUG-HUNTING25 MAINTAINERS for who that is for the subsystem you have worked on.
Dkernel-docs.txt666 list FAQ maintained by Frohwalt Egerer, who no longer maintains
668 interesting questions regarding the list, Linux, developers (who
704 kernel hacker. The audience mostly consists of people who are
Drbtree.txt201 An rbtree user who wants this feature will have to call the augmentation
Dsysrq.txt245 * I have more questions, who can I ask?
D00-INDEX91 - basic instructions for those who wants to profile Linux kernel.
DDMA-API.txt238 requirement. Therefore, it is recommended that driver writers who
DCodingStyle646 function; don't break the internal parsers of those who will read the code.
Dkernel-parameters.txt2586 Storage of the information about who allocated
2602 kmsg. This only for the users who doubt kdump always
3482 An administrator who wishes to reserve some of these
Dpinctrl.txt730 pins and who is using them, it will already have denied an impossible
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DH1940.txt37 Thanks to the many others who have also provided support.
/linux-4.1.27/arch/x86/include/asm/
De820.h20 extern void e820_print_map(char *who);
/linux-4.1.27/arch/sparc/kernel/
Dwindows.c112 void try_to_clear_window_buffer(struct pt_regs *regs, int who) in try_to_clear_window_buffer() argument
Dkernel.h171 void try_to_clear_window_buffer(struct pt_regs *regs, int who);
/linux-4.1.27/Documentation/scsi/
DFlashPoint.txt80 caused grief for many people who inadvertently purchased a system expecting
87 made available, and that Linux users who mistakenly ordered systems with
91 assist the people who initially purchased a FlashPoint for a supported
92 operating system and then later decided to run Linux, or those who had
112 are people at BusLogic who would rather not release the details of the
Dosst.txt12 will provide the OnStream support for those who are not familiar with
179 More people did help by sending useful comments. Sorry to those who have
180 been forgotten. Thanks to all the GNU/FSF and Linux developers who made this
182 Thanks go to those who tested the drivers and did send useful reports. Your
DLICENSE.qla4xxx133 entire whole, and thus to each and every part regardless of who wrote it.
187 However, parties who have received copies, or rights, from you under
217 all those who receive copies directly or indirectly through you, then
242 original copyright holder who places the Program under this License
DLICENSE.qla2xxx134 entire whole, and thus to each and every part regardless of who wrote it.
188 However, parties who have received copies, or rights, from you under
218 all those who receive copies directly or indirectly through you, then
243 original copyright holder who places the Program under this License
Din2000.txt66 about; I figure that people who are really into it will
Dlibsas.txt118 LLDD who wish to have internal port representation can make
Dncr53c8xx.txt989 confuse users who use this driver since a long time. If you desire a
1215 However, for people like me who want to enable this feature, I have added
DChangeLog.sym53c8xx258 - Add some other conditionnal code for people who have to deal
DChangeLog.1992-1997532 Patch from some undetermined individual who needs to get a life :-).
/linux-4.1.27/arch/s390/kernel/
Dcompat_wrapper.c97 COMPAT_SYSCALL_WRAP2(getpriority, int, which, int, who);
98 COMPAT_SYSCALL_WRAP3(setpriority, int, which, int, who, int, niceval);
177 COMPAT_SYSCALL_WRAP3(ioprio_set, int, which, int, who, int, ioprio);
178 COMPAT_SYSCALL_WRAP2(ioprio_get, int, which, int, who);
/linux-4.1.27/Documentation/namespaces/
Dresource-control.txt4 enabled in a kernel for people who don't trust their users or their
/linux-4.1.27/Documentation/sound/oss/
DPSS-updates1 This file contains notes for users of PSS sound cards who wish to use the
45 parameter can be used by a user who only wished to use the builtin joystick
57 all emulations whenever its unloaded. This can be useful for those who are
DESS10 people who want to use their ESS for recording sound.
DIntroduction281 mails from people who have accomplished this!
/linux-4.1.27/Documentation/filesystems/nfs/
Dfault_injection.txt36 this list is cleared, the server will have no knowledge of who the client
40 The NFS server keeps a list of what files are currently opened and who
/linux-4.1.27/Documentation/ABI/testing/
Ddebugfs-pfo-nx-crypto22 - The process ID of the process who received the most recent error from the
/linux-4.1.27/Documentation/timers/
Dtimers-howto.txt7 This question is most often faced by driver writers who have to
8 deal with hardware delays and who may not be the most intimately
/linux-4.1.27/arch/alpha/kernel/
Dosf_sys.c1137 SYSCALL_DEFINE2(osf_getrusage, int, who, struct rusage32 __user *, ru) in SYSCALL_DEFINE2() argument
1142 if (who != RUSAGE_SELF && who != RUSAGE_CHILDREN) in SYSCALL_DEFINE2()
1146 switch (who) { in SYSCALL_DEFINE2()
1398 SYSCALL_DEFINE2(osf_getpriority, int, which, int, who) in SYSCALL_DEFINE2() argument
1400 int prio = sys_getpriority(which, who); in SYSCALL_DEFINE2()
/linux-4.1.27/arch/arm/common/
Dvlock.S87 @ Check who won:
/linux-4.1.27/arch/unicore32/
DKconfig.debug30 # These options are only for real kernel hackers who want to get their hands dirty.
/linux-4.1.27/tools/power/cpupower/
DREADME39 Many thanks to Mattia Dongili who wrote the autotoolization and
/linux-4.1.27/Documentation/filesystems/
Ddlmfs.txt35 rest of this document will be geared towards those who want to use
123 Once written, an LVB will be visible to other nodes who obtain Read
Dquota.txt45 - UID of a user who caused the event
Daffs.txt107 Amiga filesystem will be owned by the user who actually mounts the
211 or manually (who would do this?). Maybe later.
Dfuse.txt31 The user who does the mounting.
35 The user who is performing filesystem operations.
Dhpfs.txt85 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
Dxfs-self-describing-metadata.txt100 Another key information point in forensic analysis is knowing who the metadata
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME.WINVIEW22 who make the audio attenuator. Their publicly available data-sheet available
DCards58 (other sound MUX setting in GPIO port needed??? somebody who fixed this???)
/linux-4.1.27/drivers/lguest/
DREADME9 equivalent) to anyone I meet who has completed this documentation.
/linux-4.1.27/drivers/scsi/
Ddc395x.c173 #define SET_RES_TARGET(who,tgt) { who &= ~RES_TARGET; who |= (int)(tgt); } argument
174 #define SET_RES_TARGET_LNX(who,tgt) { who &= ~RES_TARGET_LNX; who |= (int)(tgt) << 1; } argument
175 #define SET_RES_MSG(who,msg) { who &= ~RES_ENDMSG; who |= (int)(msg) << 8; } argument
176 #define SET_RES_DID(who,did) { who &= ~RES_DID; who |= (int)(did) << 16; } argument
177 #define SET_RES_DRV(who,drv) { who &= ~RES_DRV; who |= (int)(drv) << 24; } argument
DKconfig376 driver. Anyone wishing to use HP Smart Array controllers who
/linux-4.1.27/fs/reiserfs/
DREADME67 Real users, as opposed to folks who want to hack and then understand
97 Anatoly Pinchuk is a former member of our team who worked closely with
115 loss for me. Mikhail Gilula was a brilliant innovator who also left
/linux-4.1.27/Documentation/hwmon/
Dasb10017 supply a datasheet for these chips. Thanks go to many people who helped
Dlm8348 The driver has been successfully tested by Magnus Forsström, who I'd
Dabituguru-datasheet16 Original version by Olle Sandberg who did the heavy lifting of the initial
305 A word of caution to those who want to experiment and see if they can figure
/linux-4.1.27/Documentation/spi/
Dep93xx_spi103 Martin Guy, H. Hartley Sweeten and others who helped me during development of
/linux-4.1.27/Documentation/isdn/
DCREDITS2 I want to thank all who contributed to this project and especially to:
DREADME.gigaset35 We had also reports from users of Gigaset M105 who could use the drivers
420 and all the other people who sent logs and other information.
DINTERFACE.CAPI143 who may reuse or free it.
DREADME.HiSax462 and more people who are hunting bugs. (If I forgot somebody, please
/linux-4.1.27/Documentation/kbuild/
Dheaders_install.txt41 who create an architecture-independent tarball from the resulting include
Dmakefiles.txt91 *Users* are people who build kernels. These people type commands such as
95 *Normal developers* are people who work on features such as device
102 *Arch developers* are people who work on an entire architecture, such
106 *Kbuild developers* are people who work on the kernel build system itself.
/linux-4.1.27/Documentation/i2c/busses/
Di2c-sis96x72 To anyone else who has written w/ feedback, thanks!
/linux-4.1.27/Documentation/netlabel/
Dlsm_interface.txt10 network packets. It is intended to be used by LSM developers who want to make
/linux-4.1.27/drivers/staging/
DKconfig20 see what needs to be worked on, and who to contact.
/linux-4.1.27/Documentation/RCU/
DwhatisRCU.txt31 People who prefer starting with a conceptual overview should focus on
33 some point. People who prefer to start with an API that they can then
34 experiment with should focus on Section 2. People who prefer to start
35 with example uses should focus on Sections 3 and 4. People who need to
37 into the kernel source code. People who reason best by analogy should
80 c. At this point, there cannot be any readers who hold references
724 Or, for those who prefer a side-by-side listing:
1018 who just went out for a pizza or something. And although
1027 My thanks to the people who helped make this human-readable, including
/linux-4.1.27/net/atm/
DKconfig71 This is an experimental mechanism for users who need to terminate a
/linux-4.1.27/Documentation/usb/
Diuu_phoenix.txt61 - xmas is completely useless except for your eyes. This is one of my friend who was
Drio.txt61 also like to thank Tri Nguyen <tmn_3022000@hotmail.com> who provided use
DCREDITS157 You know who you are!
Dpersist.txt32 system woke up, who cares? It'll still work the same when you type on
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dfsl-asoc-card.txt16 Note: The card is initially designed for those sound cards who use I2S and
/linux-4.1.27/Documentation/sysctl/
DREADME12 Furthermore, the programmers who built sysctl have built it to
Dvm.txt402 who tries to access it.
/linux-4.1.27/Documentation/filesystems/cifs/
DAUTHORS47 Thanks to those in the community who have submitted detailed bug reports
DREADME66 users who are used to Windows e.g.
120 of the user who mounted the resource.
279 who executed the mount (root, except when mount.cifs
436 user who mounted the share). Letting the server (rather than
460 rwpidforward Forward pid of a process who opened a file to any read or write
/linux-4.1.27/
DCOPYING7 kernel) is copyrighted by me and others who actually wrote it.
138 entire whole, and thus to each and every part regardless of who wrote it.
192 However, parties who have received copies, or rights, from you under
222 all those who receive copies directly or indirectly through you, then
247 original copyright holder who places the Program under this License
DREPORTING-BUGS37 Identify who to notify
/linux-4.1.27/Documentation/networking/
Dregulatory.txt83 can use this to review the changes made and also review who made them
89 Device drivers who provide their own built regulatory domain
DLICENSE.qlge132 entire whole, and thus to each and every part regardless of who wrote it.
186 However, parties who have received copies, or rights, from you under
216 all those who receive copies directly or indirectly through you, then
241 original copyright holder who places the Program under this License
DLICENSE.qlcnic132 entire whole, and thus to each and every part regardless of who wrote it.
186 However, parties who have received copies, or rights, from you under
216 all those who receive copies directly or indirectly through you, then
241 original copyright holder who places the Program under this License
Ddm9000.txt16 maintained and tested by Ben Dooks, who should be CC: to any patches for this
DREADME.sb1000201 and Ralph Bonnell who are now managing the Linux SB1000 web site, and to
202 the SB1000 users who reported and helped debug the common problems listed
Deql.txt96 manager by Matt Dillon (-- "The man who sold his soul to code so much
Dnetdev-FAQ.txt160 stable, then ensure you write a decent commit log that describes who
Darcnet.txt469 For those who like diagrams, I have created two "virtual subnets" on the
Dpacket_mmap.txt62 The rest of this document is intended for people who want to understand
/linux-4.1.27/Documentation/PCI/
Dpcieaer-howto.txt80 In the example, 'Requester ID' means the ID of the device who sends
159 pci_error_handlers who consists of a couple of callback function
234 upstream ports who are attached by the service driver.
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-floppy.1996-20022 * Many thanks to Lode Leroy <Lode.Leroy@www.ibase.be>, who tested so many
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt3 This uses GPIO lines and a challenge & response mechanism to arbitrate who is
/linux-4.1.27/fs/btrfs/
DKconfig59 In most cases, unless you are a btrfs developer who needs
/linux-4.1.27/Documentation/device-mapper/
Dpersistent-data.txt17 framework for people who want to store metadata in device-mapper
/linux-4.1.27/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt5 channels and flows for the QMSS(Queue Manager SubSystem) who triggers
/linux-4.1.27/arch/arm64/
DKconfig.debug16 who are working in architecture specific areas of the kernel.
/linux-4.1.27/Documentation/power/
Ds2ram.txt25 Anyway, the way to debug this for people who are interested (have a
/linux-4.1.27/tools/usb/usbip/
DCOPYING122 entire whole, and thus to each and every part regardless of who wrote it.
176 However, parties who have received copies, or rights, from you under
206 all those who receive copies directly or indirectly through you, then
231 original copyright holder who places the Program under this License
/linux-4.1.27/drivers/staging/rtl8192e/
Dlicense125 each and every part regardless of who wrote it.
179 who have received copies, or rights, from you under this License will not
207 not permit royalty-free redistribution of the Program by all those who
231 copyright holder who places the Program under this License may add an
/linux-4.1.27/drivers/staging/rtl8192u/
Dcopying122 entire whole, and thus to each and every part regardless of who wrote it.
176 However, parties who have received copies, or rights, from you under
206 all those who receive copies directly or indirectly through you, then
231 original copyright holder who places the Program under this License
/linux-4.1.27/Documentation/ABI/
DREADME51 Users: All users of this interface who wish to be notified when
/linux-4.1.27/drivers/net/appletalk/
DKconfig82 This allows IP networking for users who only have AppleTalk
/linux-4.1.27/arch/arm/mach-omap2/
DKconfig261 users who will wish to say yes at this point - almost everyone will
/linux-4.1.27/arch/blackfin/kernel/
Dsetup.c446 static void __init print_memory_map(char *who) in print_memory_map() argument
451 printk(KERN_DEBUG " %s: %016Lx - %016Lx ", who, in print_memory_map()
/linux-4.1.27/Documentation/video4linux/
Dradiotrack.txt16 author. This document is offered in the hopes that it might help users who
DREADME.pvrusb2104 who has ever used this. It is mainly a debugging aid.
Dvideobuf349 Developers who are interested in more information can go into the relevant
/linux-4.1.27/arch/powerpc/platforms/ps3/
DKconfig40 This option is only for experts who may have the desire to fine
/linux-4.1.27/scripts/package/
Dbuilddeb323 This is useful for people who need to build external modules
/linux-4.1.27/drivers/tty/serial/8250/
DKconfig11 serial ports. The standard answer is Y. People who might say N
322 This option is intended for people who "automatically" enable this
/linux-4.1.27/Documentation/console/
Dconsole.txt89 for rebooting the kernel. For regular users who may want to switch from
/linux-4.1.27/Documentation/laptops/
Dsonypi.txt82 used in other Vaio models (like the FX series who does
/linux-4.1.27/Documentation/sound/alsa/
DREADME.maya4437 *In particular, we would appreciate testing of these functions by anyone who has access to an M/IO/…
DAudiophile-Usb.txt95 rates/depths automatically according to the user's needs. However, those who
179 Thanks to Hakan Lennestal (who discovered the Little-Endiannes of the device in
/linux-4.1.27/arch/powerpc/boot/dts/
Darches.dts12 * See file CREDITS for list of people who contributed to this
/linux-4.1.27/Documentation/virtual/kvm/
Dnested-vmx.txt73 this structure is *opaque* to its user, who is not supposed to know or care
/linux-4.1.27/Documentation/arm/nwfpe/
DREADME.FPE151 technology and for those who want to do floating point work that depends
/linux-4.1.27/drivers/tty/vt/
Ddefkeymap.c_shipped151 * Philosophy: most people do not define more strings, but they who do
/linux-4.1.27/Documentation/fmc/
Didentifiers.txt20 The first sections are only interesting for manufacturers who need to
/linux-4.1.27/arch/m32r/
DKconfig289 People using multiprocessor machines who say Y here should also say
/linux-4.1.27/Documentation/arm/
DREADME133 big external 5.25" FH 64MB drive (who could ever want more :-) ).
/linux-4.1.27/arch/x86/math-emu/
DREADME401 who I may have forgotten, please forgive me):
425 ...and numerous others who responded to my request for help with
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex111 The goal of the \UCD\ is {\em not\/} to alienate driver developers who
594 independently of the ideas of the respective author who happened to
1007 Thanks to all the people involved. First, Erik Andersen, who has
1010 Gerd Knorr, who were the first to implement this interface for SCSI
1014 Kroll, the \linux\ \cdrom\ device driver developers who were kind
/linux-4.1.27/arch/x86/
DKconfig.debug75 who are working in architecture specific areas of the kernel.
DKconfig.cpu290 This is really intended for distributors who need more
DKconfig321 People using multiprocessor machines who say Y here should also say
1802 address. This option is mainly useful for the folks who don't want
1822 is present because there are users out there who continue to use
/linux-4.1.27/Documentation/input/
Dinput-programming.txt123 call to tell those who receive the events that we've sent a complete report.
/linux-4.1.27/arch/powerpc/
DKconfig.debug338 Memory access is required for experts who want to debug the kernel.
/linux-4.1.27/Documentation/trace/
Dtracepoint-analysis.txt210 o When receiving an event about a PID, it can record who the parent was so
Dftrace-design.txt16 Ideally, everyone who wishes to retain performance while supporting tracing in
Devents.txt254 confusing (to the user who might think different filters are in
/linux-4.1.27/Documentation/sh/
Dnew-machine.txt253 way, other people who end up with this board can simply use this config
/linux-4.1.27/Documentation/powerpc/
Dcxl.txt60 who owns that acceleration function.
Dhvcs.txt464 Otherwise you have to hunt down the people who have console authority. It
/linux-4.1.27/Documentation/serial/
Dtty.txt5 the warped logic behind them. Beware all ye who read on.
/linux-4.1.27/drivers/power/
DKconfig101 as the one who is responsible for charging/discharging/monitoring
/linux-4.1.27/drivers/input/mouse/
DKconfig370 Most Dreamcast users, who have a mouse, will say Y here.
/linux-4.1.27/arch/sparc/
DKconfig172 People using multiprocessor machines who say Y here should also say
/linux-4.1.27/Documentation/cgroups/
Dcgroups.txt134 depending on who launched it (prof/student).
139 and depending on who is launching the browser he can
Dmemory.txt350 admin a unified view of memory, and it is also useful for people who just
/linux-4.1.27/fs/befs/
DChangeLog200 * Removed prototypes for functions who's definitions have been removed
/linux-4.1.27/Documentation/i2c/
Dwriting-clients1 This is a small guide for those who want to write kernel drivers for I2C
/linux-4.1.27/Documentation/devicetree/
Dbooting-without-of.txt393 chapter (who are pointed to by offsets in this header). That is,
524 root node who has no parent.
1194 to discuss possible free licensing to any vendor who wishes to
1196 (reference needed; who is 'I' here? ---gcl Jan 31, 2011)
/linux-4.1.27/arch/sh/
DKconfig681 People using multiprocessor machines who say Y here should also say
/linux-4.1.27/Documentation/fb/
Dmatroxfb.txt221 selects who is source of display clocks, whether G400, or panel.
/linux-4.1.27/Documentation/x86/
Dboot.txt232 (obligatory). Boot loaders who want to load the kernel at a
922 loader authors who need additional command line options for the boot
/linux-4.1.27/Documentation/ia64/
Derr_inject.txt18 It's especially useful for people who can not access hardware MC injection
/linux-4.1.27/mm/
DKconfig171 Users who don't use the memory hotplug feature are fine with this
/linux-4.1.27/Documentation/security/
Dcredentials.txt244 to the server, regardless of who is actually doing a read or a write upon it.
DSmack.txt295 The jargon used to talk about Smack will be familiar to those who have dealt
/linux-4.1.27/arch/arm/
DKconfig.debug12 who are working in architecture specific areas of the kernel.
78 # These options are only for real kernel hackers who want to get their hands dirty.
/linux-4.1.27/net/ipv4/
DKconfig268 attack and requires very little work from the attacker, who can
/linux-4.1.27/drivers/usb/host/
DKconfig788 This option is of interest only to developers who need to validate
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt54 who compiled and installed your kernel. Or better yet, go to the web
1134 Anyone who needs to use Speakup from your console can load his own custom
1523 parties who have received copies, or rights, from you under this
/linux-4.1.27/init/
DKconfig134 High compression options are mostly useful for users, who
1035 For those who want to have the feature enabled by default should
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1437 to create a group containing all the users who have preconfigured tap
3965 Occasionally, we hear from someone who can reach some machines, but
3966 not others on the same net, or who can reach some ports on other
/linux-4.1.27/net/netfilter/
DKconfig1262 based on who created the socket: the user or group. It is also
/linux-4.1.27/arch/mips/
DKconfig2453 People using multiprocessor machines who say Y here should also say
/linux-4.1.27/arch/m68k/ifpsp060/src/
Dpfpsp.S2027 # shift stack frame "up". who cares about <ea> field.
/linux-4.1.27/lib/
DKconfig.debug222 to keep kernel developers who have to stare a lot at assembler listings

12