Home
last modified time | relevance | path

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

12345678910>>...12

/linux/block/
A Dioprio.c85 if (!who) in SYSCALL_DEFINE3()
88 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
93 if (!who) in SYSCALL_DEFINE3()
96 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
113 if (!who) in SYSCALL_DEFINE3()
130 if (who) in SYSCALL_DEFINE3()
196 if (!who) in SYSCALL_DEFINE2()
204 if (!who) in SYSCALL_DEFINE2()
207 pgrp = find_vpid(who); in SYSCALL_DEFINE2()
223 if (!who) in SYSCALL_DEFINE2()
[all …]
/linux/drivers/gpu/drm/i915/selftests/
A Dscatterlist.c44 const char *who, in expect_pfn_sg() argument
57 __func__, who, pfn, page_to_pfn(page)); in expect_pfn_sg()
67 if (igt_timeout(timeout, "%s timed out\n", who)) in expect_pfn_sg()
74 __func__, who, pt->end, pfn); in expect_pfn_sg()
82 const char *who, in expect_pfn_sg_page_iter() argument
94 __func__, who, pfn, page_to_pfn(page)); in expect_pfn_sg_page_iter()
105 __func__, who, pt->end, pfn); in expect_pfn_sg_page_iter()
113 const char *who, in expect_pfn_sgtiter() argument
135 __func__, who, pt->end, pfn); in expect_pfn_sgtiter()
145 const char *who, in expect_pfn_sgtable() argument
[all …]
/linux/arch/s390/kvm/
A Dtrace-s390.h126 TP_PROTO(__u64 type, __u32 parm, __u64 parm64, int who),
127 TP_ARGS(type, parm, parm64, who),
133 __field(int, who)
140 __entry->who = who;
144 (__entry->who == 1) ? " (from kernel)" :
145 (__entry->who == 2) ? " (from user)" : "",
/linux/fs/
A Dsuper.c1965 WARN_ON_ONCE((who & ~FREEZE_FLAGS)); in freeze_inc()
1968 if (who & FREEZE_HOLDER_KERNEL) in freeze_inc()
1970 if (who & FREEZE_HOLDER_USERSPACE) in freeze_inc()
1992 if (who & FREEZE_HOLDER_KERNEL) in may_freeze()
1993 return (who & FREEZE_MAY_NEST) || in may_freeze()
1995 if (who & FREEZE_HOLDER_USERSPACE) in may_freeze()
1996 return (who & FREEZE_MAY_NEST) || in may_freeze()
2068 if (may_freeze(sb, who)) in freeze_super()
2162 if (freeze_dec(sb, who)) in thaw_super_locked()
2177 freeze_inc(sb, who); in thaw_super_locked()
[all …]
A Dfcntl.c154 int f_setown(struct file *filp, int who, int force) in f_setown() argument
163 if (who < 0) { in f_setown()
165 if (who == INT_MIN) in f_setown()
169 who = -who; in f_setown()
177 if (who) { in f_setown()
178 pid = find_vpid(who); in f_setown()
/linux/kernel/
A Dsys.c249 if (who) in SYSCALL_DEFINE3()
257 if (who) in SYSCALL_DEFINE3()
258 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
270 if (!who) in SYSCALL_DEFINE3()
312 if (who) in SYSCALL_DEFINE2()
323 if (who) in SYSCALL_DEFINE2()
324 pgrp = find_vpid(who); in SYSCALL_DEFINE2()
338 if (!who) in SYSCALL_DEFINE2()
1816 switch (who) { in getrusage()
1884 if (who != RUSAGE_SELF && who != RUSAGE_CHILDREN && in SYSCALL_DEFINE2()
[all …]
/linux/Documentation/process/
A D1.Intro.rst64 those products attractive to Linux users. Embedded systems vendors, who
67 other software vendors who base their products on Linux have a clear
92 experience behind it. A developer who does not understand the kernel
93 community's ways (or, worse, who tries to flout or circumvent them) will
95 being helpful to those who are trying to learn, has little time for those
96 who will not listen or who do not care about the development process.
98 It is hoped that those who read this document will be able to avoid that
101 community is always in need of developers who will help to make the kernel
102 better; the following text should help you - or those who work for you -
149 result of a simple rule requiring any developer who makes an API change
[all …]
A D5.Posting.rst30 patches which are known to be half-baked, but those who do will come in
110 users who are engaging in the noble work of tracking down problems.
144 enough for a reader who sees it with no other context to figure out the
165 These include subsystem maintainers and reviewers who need to decide
169 chasing, users who want to know how the kernel has changed, and more. A
261 - Reported-by: names a user who reported a problem which is fixed by this
263 people who test our code and let us know when things do not work
305 When mailing patches, it is important to send copies to anybody who might
314 - Other developers who have been working in the same area - especially
315 those who might be working there now. Using git to see who else has
[all …]
A D3.Early-stage.rst139 MAINTAINERS file may, in fact, not be the person who is actually acting in
140 that role currently. So, when there is doubt about who to contact, a
141 useful trick is to use git (and "git log" in particular) to see who is
142 currently active within the subsystem of interest. Look at who is writing
143 patches, and who, if anybody, is attaching Signed-off-by lines to those
144 patches. Those are the people who will be best placed to help with a new
156 command line, it will list the maintainers who should probably receive
161 developers who have no real interest in the code you are modifying.
A Dembargoed-hardware-issues.rst35 is a private list of security officers who will help you coordinate a fix
47 vendor, we welcome contact from researchers or individuals who have
98 The hardware security team identifies the developers (domain experts) who
140 developers (domain experts) who should be informed initially about the
154 entities who have already been, or should be, informed about the issue.
160 - The disclosed entities can be contacted to name experts who should
163 - If an expert who is required to handle an issue is employed by a listed
226 to any individual who is not a member of the response team nor to any other
284 organizations, who can answer questions about or provide guidance on the
342 Disclosed parties who want to participate in the communication send a list
A Dmanagement-style.rst7 on who you ask) management style for the linux kernel. It's meant to
18 lead persons, not the people who do traditional management inside
111 This preemptive admission of incompetence might also make the people who
176 trust somebody who is so clearly hiding their true character.
196 Suck up to them, because they are the people who will make your job
225 person who lost their whole 36GB porn-collection because of your
229 Then make the developer who really screwed up (if you can find them) know
232 importantly, they're also likely the person who can fix it. Because, let's
237 glory, because you're the one who gets to say "I screwed up". And if
265 without making it painful to the recipient, who just thinks you're being
A Ddevelopment-process.rst9 accessible to those who are not intimately familiar with Linux kernel
/linux/Documentation/filesystems/xfs/
A Dxfs-maintainer-entry-profile.rst31 - **Outside Contributor**: Anyone who sends a patch but is not involved
33 These folks are usually people who work on other filesystems or
36 - **Developer**: Someone who is familiar with the XFS codebase enough to
42 - **Senior Developer**: A developer who is very familiar with at least
51 - **Reviewer**: Someone (most likely also a developer) who reads code
71 - **Bug Triager**: Someone who examines incoming bug reports in just
95 - **LTS Maintainer**: Someone who backports and tests bug fixes from
/linux/Documentation/block/
A Dioprio.rst86 static inline int ioprio_set(int which, int who, int ioprio)
88 return syscall(__NR_ioprio_set, which, who, ioprio);
91 static inline int ioprio_get(int which, int who)
93 return syscall(__NR_ioprio_get, which, who);
/linux/arch/x86/kernel/
A De820.c203 void __init e820__print_table(char *who) in e820__print_table() argument
209 who, in e820__print_table()
1251 char *who = "BIOS-e820"; in e820__memory_setup_default() local
1265 who = "BIOS-88"; in e820__memory_setup_default()
1268 who = "BIOS-e801"; in e820__memory_setup_default()
1279 return who; in e820__memory_setup_default()
1289 char *who; in e820__memory_setup() local
1294 who = x86_init.resources.memory_setup(); in e820__memory_setup()
1300 e820__print_table(who); in e820__memory_setup()
/linux/include/linux/
A Dresource.h10 void getrusage(struct task_struct *p, int who, struct rusage *ru);
/linux/fs/nfsd/
A Dacl.h46 __be32 nfs4_acl_write_who(struct xdr_stream *xdr, int who);
/linux/Documentation/admin-guide/sysctl/
A Duser.rst25 the user in the user namespace who created the object and
29 who created user namespaces the creation of the object happens
/linux/Documentation/virt/kvm/s390/
A Ds390-pv-dump.rst16 confidentiality until the dump is in the hands of the VM owner who
19 The confidentiality of the VM dump is ensured by the Ultravisor who
/linux/Documentation/scsi/
A DFlashPoint.rst93 caused grief for many people who inadvertently purchased a system expecting
100 made available, and that Linux users who mistakenly ordered systems with
104 assist the people who initially purchased a FlashPoint for a supported
105 operating system and then later decided to run Linux, or those who had
125 are people at BusLogic who would rather not release the details of the
/linux/drivers/virt/coco/sev-guest/
A DKconfig11 the PSP without risk from a malicious hypervisor who wishes to read,
/linux/Documentation/driver-api/
A Dwbrf.rst26 Producer: such component who can produce high-powered radio frequency
27 Consumer: such component who can adjust its in-use frequency in
/linux/Documentation/devicetree/bindings/eeprom/
A Dat25.yaml18 # There are multiple known vendors who manufacture EEPROM chips compatible
22 # "atmel,at25" part and should be fixed by somebody who knows vendor and
/linux/arch/sparc/kernel/
A Dwindows.c113 void try_to_clear_window_buffer(struct pt_regs *regs, int who) in try_to_clear_window_buffer() argument
/linux/tools/testing/selftests/net/mptcp/
A Dmptcp_sockopt.sh236 local who=$2
241 echo "Created $name (size $size KB) containing data sent by $who"

Completed in 48 milliseconds

12345678910>>...12