Home
last modified time | relevance | path

Searched refs:who (Results 1 – 25 of 199) sorted by relevance

12345678

/linux-3.4.99/fs/
Dioprio.c61 SYSCALL_DEFINE3(ioprio_set, int, which, int, who, int, ioprio) in SYSCALL_DEFINE3() argument
94 if (!who) in SYSCALL_DEFINE3()
97 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
102 if (!who) in SYSCALL_DEFINE3()
105 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
113 if (!who) in SYSCALL_DEFINE3()
116 user = find_user(who); in SYSCALL_DEFINE3()
122 if (__task_cred(p)->uid != who) in SYSCALL_DEFINE3()
129 if (who) in SYSCALL_DEFINE3()
172 SYSCALL_DEFINE2(ioprio_get, int, which, int, who) in SYSCALL_DEFINE2() argument
[all …]
Dfcntl.c236 int who = arg; in f_setown() local
239 if (who < 0) { in f_setown()
241 who = -who; in f_setown()
244 pid = find_vpid(who); in f_setown()
/linux-3.4.99/drivers/scsi/
Dtmscsim.h270 #define SET_RES_TARGET(who, tgt) do { who &= ~RES_TARGET; who |= (int)(tgt); } while (0) argument
271 #define SET_RES_TARGET_LNX(who, tgt) do { who &= ~RES_TARGET_LNX; who |= (int)(tgt) << 1; } while (… argument
272 #define SET_RES_MSG(who, msg) do { who &= ~RES_ENDMSG; who |= (int)(msg) << 8; } while (0) argument
273 #define SET_RES_DID(who, did) do { who &= ~RES_DID; who |= (int)(did) << 16; } while (0) argument
274 #define SET_RES_DRV(who, drv) do { who &= ~RES_DRV; who |= (int)(drv) << 24; } while (0) argument
/linux-3.4.99/kernel/
Dsys.c173 SYSCALL_DEFINE3(setpriority, int, which, int, who, int, niceval) in SYSCALL_DEFINE3() argument
195 if (who) in SYSCALL_DEFINE3()
196 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
203 if (who) in SYSCALL_DEFINE3()
204 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
213 if (!who) in SYSCALL_DEFINE3()
214 who = cred->uid; in SYSCALL_DEFINE3()
215 else if ((who != cred->uid) && in SYSCALL_DEFINE3()
216 !(user = find_user(who))) in SYSCALL_DEFINE3()
220 if (__task_cred(p)->uid == who) in SYSCALL_DEFINE3()
[all …]
/linux-3.4.99/fs/nfsd/
Dacl.h46 int nfs4_acl_write_who(int who, char *p);
48 uid_t who, u32 mask);
Dnfs4acl.c267 ace->who = pa->e_id; in _posix_to_nfsv4_one()
276 ace->who = pa->e_id; in _posix_to_nfsv4_one()
303 ace->who = pa->e_id; in _posix_to_nfsv4_one()
332 ace->who = pa->e_id; in _posix_to_nfsv4_one()
640 i = find_uid(state, state->users, ace->who); in process_one_v4_ace()
662 i = find_uid(state, state->groups, ace->who); in process_one_v4_ace()
824 nfs4_acl_write_who(int who, char *p) in nfs4_acl_write_who() argument
829 if (s2t_map[i].type == who) { in nfs4_acl_write_who()
/linux-3.4.99/arch/powerpc/kernel/
Dsys_ppc32.c473 long compat_sys_getpriority(u32 which, u32 who) in compat_sys_getpriority() argument
476 return sys_getpriority((int)which, (int)who); in compat_sys_getpriority()
479 long compat_sys_setpriority(u32 which, u32 who, u32 niceval) in compat_sys_setpriority() argument
482 return sys_setpriority((int)which, (int)who, (int)niceval); in compat_sys_setpriority()
485 long compat_sys_ioprio_get(u32 which, u32 who) in compat_sys_ioprio_get() argument
488 return sys_ioprio_get((int)which, (int)who); in compat_sys_ioprio_get()
491 long compat_sys_ioprio_set(u32 which, u32 who, u32 ioprio) in compat_sys_ioprio_set() argument
494 return sys_ioprio_set((int)which, (int)who, (int)ioprio); in compat_sys_ioprio_set()
/linux-3.4.99/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
355 Among the kernel developers who do not use git, the most popular choice is
380 represent a potential hazard to developers, who risk getting buried under a
397 development community comes together as a whole; developers who avoid this
409 without changing the email subject line) and the people who are
423 questions. Some developers can get impatient with people who clearly
435 beginning developers to go wrong. Somebody who asks a networking-related
[all …]
/linux-3.4.99/arch/x86/kernel/
De820.c156 void __init e820_print_map(char *who) in e820_print_map() argument
161 printk(KERN_INFO " %s: %016Lx - %016Lx ", who, in e820_print_map()
1008 char *who = "BIOS-e820"; in default_machine_specific_memory_setup() local
1029 who = "BIOS-88"; in default_machine_specific_memory_setup()
1032 who = "BIOS-e801"; in default_machine_specific_memory_setup()
1041 return who; in default_machine_specific_memory_setup()
1046 char *who; in setup_memory_map() local
1048 who = x86_init.resources.memory_setup(); in setup_memory_map()
1051 e820_print_map(who); in setup_memory_map()
/linux-3.4.99/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-3.4.99/drivers/w1/slaves/
DKconfig66 as the one who is responsible for charging/discharging/monitoring
79 as the one who is responsible for charging/discharging/monitoring
92 as the one who is responsible for charging/discharging/monitoring
/linux-3.4.99/arch/ia64/kernel/
Dsys_ia64.c81 ia64_getpriority (int which, int who) in ia64_getpriority() argument
85 prio = sys_getpriority(which, who); in ia64_getpriority()
/linux-3.4.99/Documentation/dvb/
Dreadme.txt39 is the who-is-who of DVB development.
/linux-3.4.99/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
/linux-3.4.99/include/linux/
Dresource.h83 int getrusage(struct task_struct *p, int who, struct rusage __user *ru);
/linux-3.4.99/arch/sparc/kernel/
Dwindows.c109 void try_to_clear_window_buffer(struct pt_regs *regs, int who) in try_to_clear_window_buffer() argument
/linux-3.4.99/Documentation/arm/Samsung-S3C24XX/
DH1940.txt37 Thanks to the many others who have also provided support.
/linux-3.4.99/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
/linux-3.4.99/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
/linux-3.4.99/arch/x86/include/asm/
De820.h87 extern void e820_print_map(char *who);
/linux-3.4.99/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-3.4.99/arch/s390/
DKconfig.debug16 Memory access is required for experts who want to debug the kernel.

12345678