Home
last modified time | relevance | path

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

/linux/drivers/iommu/
H A Dsun50i-iommu.c883 u32 blame; in sun50i_iommu_handle_pt_irq() local
888 blame = iommu_read(iommu, blame_reg); in sun50i_iommu_handle_pt_irq()
889 master = ilog2(blame & IOMMU_INT_MASTER_MASK); in sun50i_iommu_handle_pt_irq()
907 u32 blame; in sun50i_iommu_handle_perm_irq() local
911 blame = iommu_read(iommu, IOMMU_INT_STA_REG); in sun50i_iommu_handle_perm_irq()
912 master = ilog2(blame & IOMMU_INT_MASTER_MASK); in sun50i_iommu_handle_perm_irq()
/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 Dbackporting.rst194 git blame
198 one for a given conflict) is to run ``git blame``. In this case, you
202 git blame <commit>^ -- <path>
208 git blame -L:'\<function\>' <commit>^ -- <path>
211 the blame output is the commit ID of the patch that added a given line
219 the latter case, you may have to run ``git blame`` again and specify the
466 to these areas as ``git blame`` won't show you code that has been
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
/linux/Documentation/usb/
H A Diuu_phoenix.rst16 guru, so don't blame me if your system is unstable
/linux/Documentation/translations/zh_CN/process/
H A Dmaintainer-pgp-guide.rst575 .. _`自己与它无关`: https://github.com/jayphelps/git-blame-someone-else
/linux/Documentation/driver-api/acpi/
H A Dlinuxized-acpica.rst268 "git blame source/include/acpixf.h" and referencing the line that contains
/linux/Documentation/admin-guide/RAS/
H A Dmain.rst195 to blame. So, it has to blame both memory modules.
201 way to know what memory module is to blame. So, it has to blame both
/linux/Documentation/driver-api/usb/
H A Dpersist.rst161 data corruption and to crash your system. You'll have no one to blame
/linux/Documentation/translations/sp_SP/process/
H A Dmaintainer-kvm-x86.rst255 serie de "git blame", los detalles de cada cambio a lo largo del camino son
/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
/linux/Documentation/driver-api/
H A Dipmi.rst486 interrupts, the driver will run VERY slowly. Don't blame me,