Home
last modified time | relevance | path

Searched full:who (Results 1 – 25 of 693) sorted by relevance

12345678910>>...28

/linux/block/
H A Dioprio.c65 SYSCALL_DEFINE3(ioprio_set, int, which, int, who, int, ioprio) in SYSCALL_DEFINE3() argument
81 if (!who) in SYSCALL_DEFINE3()
84 p = find_task_by_vpid(who); in SYSCALL_DEFINE3()
89 if (!who) in SYSCALL_DEFINE3()
92 pgrp = find_vpid(who); in SYSCALL_DEFINE3()
106 uid = make_kuid(current_user_ns(), who); in SYSCALL_DEFINE3()
109 if (!who) in SYSCALL_DEFINE3()
126 if (who) in SYSCALL_DEFINE3()
180 SYSCALL_DEFINE2(ioprio_get, int, which, int, who) in SYSCALL_DEFINE2() argument
192 if (!who) in SYSCALL_DEFINE2()
[all …]
/linux/Documentation/process/
H 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 -
115 Amanda McPherson, who saw the value of this effort and made it all happen.
[all …]
H A D3.Early-stage.rst63 - Who are the users affected by this problem? Which use cases should the
125 Who do you talk to?
139 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.
H 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
H 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
H A D2.Process.rst59 allowed, but such occasions are rare; developers who try to merge new
212 There is exactly one person who can merge patches into the mainline kernel
223 who has overall responsibility for the code within that subsystem. These
225 of the kernel they manage; they are the ones who will (usually) accept a
365 Among the kernel developers who do not use git, the most popular choice is
391 represent a potential hazard to developers, who risk getting buried under a
408 development community comes together as a whole; developers who avoid this
420 without changing the email subject line) and the people who are
434 questions. Some developers can get impatient with people who clearly
447 beginning developers to go wrong. Somebody who asks a networking-related
[all …]
H A D6.Followthrough.rst40 people remember who wrote kernel code, but there is little lasting fame
41 for those who reviewed it. So reviewers can get grumpy, especially when
152 may be a new round of comments from developers who had not been aware of
155 though; you still need to be responsive to developers who have questions or
186 development community remembers developers who lose interest in their code
/linux/fs/
H A Dsuper.c42 static int thaw_super_locked(struct super_block *sb, enum freeze_holder who,
1953 static inline int freeze_inc(struct super_block *sb, enum freeze_holder who) in freeze_inc() argument
1955 WARN_ON_ONCE((who & ~FREEZE_FLAGS)); in freeze_inc()
1956 WARN_ON_ONCE(hweight32(who & FREEZE_HOLDERS) > 1); in freeze_inc()
1958 if (who & FREEZE_HOLDER_KERNEL) in freeze_inc()
1960 if (who & FREEZE_HOLDER_USERSPACE) in freeze_inc()
1965 static inline int freeze_dec(struct super_block *sb, enum freeze_holder who) in freeze_dec() argument
1967 WARN_ON_ONCE((who & ~FREEZE_FLAGS)); in freeze_dec()
1968 WARN_ON_ONCE(hweight32(who & FREEZE_HOLDERS) > 1); in freeze_dec()
1970 if ((who & FREEZE_HOLDER_KERNEL) && sb->s_writers.freeze_kcount) in freeze_dec()
[all …]
/linux/arch/s390/kvm/
H 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/Documentation/block/
H 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/Documentation/scsi/
H 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/tools/perf/pmu-events/arch/x86/rocketlake/
H A Dfrontend.json41 "BriefDescription": "Retired Instructions who experienced DSB miss.",
52 "BriefDescription": "Retired Instructions who experienced a critical DSB miss.",
63 "BriefDescription": "Retired Instructions who experienced iTLB true miss.",
74 "BriefDescription": "Retired Instructions who experienced Instruction L1 Cache true miss.",
80 "PublicDescription": "Counts retired Instructions who experienced Instruction L1 Cache true miss.",
85 "BriefDescription": "Retired Instructions who experienced Instruction L2 Cache true miss.",
91 "PublicDescription": "Counts retired Instructions who experienced Instruction L2 Cache true miss.",
217 "BriefDescription": "Retired Instructions who experienced STLB (2nd level TLB) true miss.",
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A Dfrontend.json41 "BriefDescription": "Retired Instructions who experienced DSB miss.",
52 "BriefDescription": "Retired Instructions who experienced a critical DSB miss.",
63 "BriefDescription": "Retired Instructions who experienced iTLB true miss.",
74 "BriefDescription": "Retired Instructions who experienced Instruction L1 Cache true miss.",
80 "PublicDescription": "Counts retired Instructions who experienced Instruction L1 Cache true miss.",
85 "BriefDescription": "Retired Instructions who experienced Instruction L2 Cache true miss.",
91 "PublicDescription": "Counts retired Instructions who experienced Instruction L2 Cache true miss.",
217 "BriefDescription": "Retired Instructions who experienced STLB (2nd level TLB) true miss.",
/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A Dfrontend.json41 "BriefDescription": "Retired Instructions who experienced DSB miss.",
52 "BriefDescription": "Retired Instructions who experienced a critical DSB miss.",
63 "BriefDescription": "Retired Instructions who experienced iTLB true miss.",
74 "BriefDescription": "Retired Instructions who experienced Instruction L1 Cache true miss.",
80 "PublicDescription": "Counts retired Instructions who experienced Instruction L1 Cache true miss.",
85 "BriefDescription": "Retired Instructions who experienced Instruction L2 Cache true miss.",
91 "PublicDescription": "Counts retired Instructions who experienced Instruction L2 Cache true miss.",
217 "BriefDescription": "Retired Instructions who experienced STLB (2nd level TLB) true miss.",
/linux/tools/perf/pmu-events/arch/x86/icelake/
H A Dfrontend.json41 "BriefDescription": "Retired Instructions who experienced DSB miss.",
52 "BriefDescription": "Retired Instructions who experienced a critical DSB miss.",
63 "BriefDescription": "Retired Instructions who experienced iTLB true miss.",
74 "BriefDescription": "Retired Instructions who experienced Instruction L1 Cache true miss.",
80 "PublicDescription": "Counts retired Instructions who experienced Instruction L1 Cache true miss.",
85 "BriefDescription": "Retired Instructions who experienced Instruction L2 Cache true miss.",
91 "PublicDescription": "Counts retired Instructions who experienced Instruction L2 Cache true miss.",
217 "BriefDescription": "Retired Instructions who experienced STLB (2nd level TLB) true miss.",
/linux/Documentation/mm/
H A Dpage_owner.rst2 page owner: Tracking about who allocated each page
8 page owner is for the tracking about who allocated each page.
16 using it for analyzing who allocate each page is rather complex. We need
141 See the result about who allocated each page
/linux/Documentation/virt/kvm/s390/
H 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/LICENSES/preferred/
H A DLGPL-2.139 Foundation and other authors who decide to use it. You can use it too, but
208 whole, and thus to each and every part regardless of who wrote it.
301 Library. (It is understood that the user who changes the contents of
357 License. However, parties who have received copies, or rights, from you
387 those who receive copies directly or indirectly through you, then the
412 copyright holder who places the Library under this License may add an
453 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
H A DGPL-2.0141 entire whole, and thus to each and every part regardless of who wrote it.
195 However, parties who have received copies, or rights, from you under
225 all those who receive copies directly or indirectly through you, then
250 original copyright holder who places the Program under this License
290 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
H A DLGPL-2.0196 whole, and thus to each and every part regardless of who wrote it.
289 Library. (It is understood that the user who changes the contents of
337 License. However, parties who have received copies, or rights, from you
367 those who receive copies directly or indirectly through you, then the
392 copyright holder who places the Library under this License may add an
433 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
/linux/Documentation/driver-api/
H 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/admin-guide/sysctl/
H 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/tools/usb/usbip/
H A 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
271 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
/linux/fs/nfs_common/
H A Dgrace.c20 * @lm: who this grace period is for
46 * @lm: who this grace period is for
/linux/Documentation/devicetree/bindings/eeprom/
H 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

12345678910>>...28