Home
last modified time | relevance | path

Searched refs:blame (Results 1 – 17 of 17) sorted by relevance

/openbmc/qemu/
H A D.git-blame-ignore-revs2 # List of code-formatting clean ups the git blame can ignore
4 # git blame --ignore-revs-file .git-blame-ignore-revs
8 # git config blame.ignoreRevsFile .git-blame-ignore-revs
/openbmc/linux/drivers/iommu/
H A Dsun50i-iommu.c869 u32 blame; in sun50i_iommu_handle_pt_irq() local
874 blame = iommu_read(iommu, blame_reg); in sun50i_iommu_handle_pt_irq()
875 master = ilog2(blame & IOMMU_INT_MASTER_MASK); in sun50i_iommu_handle_pt_irq()
893 u32 blame; in sun50i_iommu_handle_perm_irq() local
897 blame = iommu_read(iommu, IOMMU_INT_STA_REG); in sun50i_iommu_handle_perm_irq()
898 master = ilog2(blame & IOMMU_INT_MASTER_MASK); in sun50i_iommu_handle_perm_irq()
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DGLWTPL17 TRACE TO TRACK THE AUTHOR of the original product to blame for or hold
/openbmc/linux/Documentation/process/
H A Dmanagement-style.rst216 4) Placing blame
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
221 It's not actually that hard to accept the blame, especially if people
223 best way of taking the blame: do it for someone else. You'll feel good
235 Taking the blame is also why you get to be manager in the first place.
278 Since your main responsibility seems to be to take the blame for other
H A Dmaintainer-pgp-guide.rst53 shift the blame for potential future security incidents to someone else.
669 .. _`nothing to do with it`: https://github.com/jayphelps/git-blame-someone-else
H A Dmaintainer-kvm-x86.rst211 E.g. when doing a series of "git blame", the details of each change along the
/openbmc/linux/Documentation/usb/
H A Diuu_phoenix.rst16 guru, so don't blame me if your system is unstable
/openbmc/openbmc/meta-arm/ci/
H A Dpatchreview258 summary = analyse(results, want_blame=args.blame, verbose=args.verbose)
/openbmc/openbmc/poky/scripts/contrib/
H A Dpatchreview.py252 analyse(results, want_blame=args.blame, verbose=args.verbose)
/openbmc/linux/Documentation/driver-api/acpi/
H A Dlinuxized-acpica.rst268 "git blame source/include/acpixf.h" and referencing the line that contains
/openbmc/linux/Documentation/admin-guide/
H A Dras.rst191 to blame. So, it has to blame both memory modules.
197 way to know what memory module is to blame. So, it has to blame both
/openbmc/linux/Documentation/driver-api/usb/
H A Dpersist.rst161 data corruption and to crash your system. You'll have no one to blame
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dkernel-yocto.bbclass541 …ol_why.py', '--dotconfig', '{}'.format( d.getVar('B') + '/.config' ), '--blame', c], cwd=s, env=e…
/openbmc/docs/
H A Danti-patterns.md32 running git blame and look at who wrote the code originally, and ask them on the
/openbmc/linux/Documentation/translations/it_IT/process/
H A Dmaintainer-pgp-guide.rst690 .. _`non averci niente a che fare`: https://github.com/jayphelps/git-blame-someone-else
/openbmc/linux/Documentation/driver-api/
H A Dipmi.rst486 interrupts, the driver will run VERY slowly. Don't blame me,
/openbmc/u-boot/tools/buildman/
H A DREADME585 to blame our commits. The bad news is that our commits are not tested on that