/openbmc/openbmc/poky/ |
H A D | MEMORIAM | 1 Some project contributors who are sadly no longer with us:
|
/openbmc/linux/Documentation/process/ |
H A D | 3.Early-stage.rst | 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 D | management-style.rst | 7 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 D | embargoed-hardware-issues.rst | 35 is a private list of security officers who will help you to coordinate a 47 vendor, we welcome contact from researchers or individuals who have 98 The hardware security team identifies the developers (domain experts) who 138 developers (domain experts) who should be informed initially about the 152 entities who have already been, or should be, informed about the issue. 158 - The disclosed entities can be contacted to name experts who should 246 organizations, who can answer questions about or provide guidance on the 303 Subscription is handled by the response teams. Disclosed parties who want
|
H A D | development-process.rst | 24 accessible to those who are not intimately familiar with Linux kernel
|
/openbmc/docs/security/ |
H A D | obmc-security-response-team.md | 37 communication vehicle between the person who reported the problem and the 43 contain collected wisdom for the response team and community members who are
|
/openbmc/phosphor-networkd/ |
H A D | OWNERS | 17 # * owners: A list of individuals who have approval authority on the 20 # * reviewers: A list of individuals who have requested review notification
|
/openbmc/dbus-sensors/ |
H A D | OWNERS | 17 # * owners: A list of individuals who have approval authority on the 20 # * reviewers: A list of individuals who have requested review notification
|
/openbmc/phosphor-host-ipmid/ |
H A D | OWNERS | 17 # * owners: A list of individuals who have approval authority on the 20 # * reviewers: A list of individuals who have requested review notification
|
/openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-security/bastille/files/ |
H A D | HPSpecific.pm | 464 my $who = &getGlobal('BIN', "who") . " -r"; 465 my $levelInfo = `$who`; 467 &B_log("WARNING","Unable to use \"$who\" to determine system run.\n" . 483 &B_log("WARNING","Unable to use \"$who\" to determine system run.\n" . 1284 my $who = &getGlobal("BIN", "who"); 1285 my $runlevel = &B_Backtick("$who -r");
|
/openbmc/openbmc-test-automation/ffdc/templates/ |
H A D | env_vars_template.yaml | 1 # This is config file for user who wants to load pre-define variables
|
/openbmc/openbmc/poky/meta/recipes-core/os-release/ |
H A D | os-release.bb | 33 # understand people will want to identify themselves as the people who 36 # This end result combines to mean systems can be traced back to both who
|
/openbmc/docs/ |
H A D | OWNERS | 17 # * owners: A list of individuals who have approval authority on the 20 # * reviewers: A list of individuals who have requested review notification
|
/openbmc/pldm/ |
H A D | OWNERS | 17 # * owners: A list of individuals who have approval authority on the 20 # * reviewers: A list of individuals who have requested review notification
|
/openbmc/linux/Documentation/admin-guide/sysctl/ |
H A D | user.rst | 25 the user in the user namespace who created the object and 29 who created user namespaces the creation of the object happens
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | CDLA-Permissive-2.0 | 31 5.2. "Data Provider" means any person who is the source of Data provided under this agreement and i… 33 5.3. "Data Recipient" means any person who receives Data directly or indirectly from a Data Provide…
|
H A D | XSkat | 10 2.b) It is clearly stated who last changed the program. The program is renamed or the version numbe…
|
H A D | TAPR-OHL-1.0 | 20 your freedom to share and to create. It forbids anyone who receives 32 those who benefit from an OHL design may not bring lawsuits claiming that 52 available without charge for at least three years to anyone who requests 61 developers who have provided their email address. This is a good 135 Agreement unless they are specifically excluded. Each person who 144 from suit granted in Section 2), but the rights of others who have 192 Section 4 to each Licensor who has provided an email address with the 229 person who requests it; or (ii) a URL where that Documentation may be
|
H A D | SAX-PD | 12 … law or agreed to in writing will any copyright holder, or any other party who may modify and/or r… 16 This page includes statements to that effect by David Megginson, who would have been able to claim …
|
H A D | GD | 3 …e authors who have required such a statement. If you are aware of any oversights in this copyrigh…
|
/openbmc/linux/drivers/virt/coco/sev-guest/ |
H A D | Kconfig | 10 the PSP without risk from a malicious hypervisor who wishes to read,
|
/openbmc/linux/Documentation/virt/kvm/s390/ |
H A D | s390-pv-dump.rst | 16 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
|
/openbmc/linux/arch/x86/include/asm/e820/ |
H A D | api.h | 21 extern void e820__print_table(char *who);
|
/openbmc/linux/arch/sparc/kernel/ |
H A D | windows.c | 113 void try_to_clear_window_buffer(struct pt_regs *regs, int who) in try_to_clear_window_buffer() argument
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/websocketpp/websocketpp-0.8.2/ |
H A D | 855.patch | 19 ….0" "1.40.0" "1.41.0" "1.42.0" "1.43.0" "1.44.0" "1.46.1") # todo: someone who knows better spesif…
|