Home
last modified time | relevance | path

Searched refs:MAINTAINER (Results 1 – 25 of 28) sorted by relevance

12

/openbmc/phosphor-pcie-presence/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/openpower-sbe-interface/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/phosphor-mboxd/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/pyphosphor/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/inarp/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/openpower-inventory-upload/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/openpower-logging/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/phosphor-event/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/boost-dbus/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/google-ipmi-sys/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/libbej/
H A DMAINTAINERS39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
/openbmc/linux/drivers/cpufreq/
H A Dspeedstep-centrino.c33 #define MAINTAINER "linux-pm@vger.kernel.org" macro
248 "send /proc/cpuinfo to " MAINTAINER "\n", in centrino_cpu_init_table()
372 MAINTAINER "\n"); in centrino_cpu_init()
/openbmc/openbmc/poky/meta-poky/conf/distro/
H A Dpoky.conf9 MAINTAINER = "Poky Maintainers <poky@lists.yoctoproject.org>"
/openbmc/qemu/tests/docker/dockerfiles/
H A Dpython.docker4 MAINTAINER John Snow <jsnow@redhat.com>
H A Ddebian-tricore-cross.docker14 MAINTAINER Philippe Mathieu-Daudé <f4bug@amsat.org>
/openbmc/qemu/.gitlab-ci.d/opensbi/
H A DDockerfile6 MAINTAINER Bin Meng <bmeng.cn@gmail.com>
/openbmc/openbmc/poky/documentation/ref-manual/
H A Dvarlocality.rst34 - :term:`MAINTAINER`
/openbmc/openbmc/poky/meta/classes-global/
H A Dpackage_ipk.bbclass134 fields.append(["Maintainer: %s\n", ['MAINTAINER']])
257 IPKEXTRAVARS = "PRIORITY MAINTAINER PACKAGE_ARCH HOMEPAGE PACKAGE_ADD_METADATA_IPK"
H A Dpackage_deb.bbclass121 fields.append(["Maintainer: %s\n", ['MAINTAINER']])
294 DEBEXTRAVARS = "PKGV PKGR PKGV DESCRIPTION SECTION PRIORITY MAINTAINER DPKG_ARCH PN HOMEPAGE PACKAG…
/openbmc/openbmc/poky/meta/recipes-support/vim/
H A Dvim.inc79 --with-modified-by='${MAINTAINER}' \
/openbmc/openbmc/poky/meta/conf/
H A Ddocumentation.conf289 MAINTAINER[doc] = "The email address of the distribution maintainer."
H A Dbitbake.conf299 MAINTAINER = "OE-Core Developers <openembedded-core@lists.openembedded.org>"
/openbmc/openbmc/poky/documentation/migration-guides/
H A Drelease-notes-4.0.9.rst115 - vim: set modified-by to the recipe MAINTAINER
H A Drelease-notes-4.1.4.rst133 - vim: set modified-by to the recipe :term:`MAINTAINER`
/openbmc/linux/Documentation/translations/it_IT/doc-guide/
H A Dkernel-doc.rst44 discrezione dal manutentore (MAINTAINER) del file sorgente.
59 più bassa ed è a discrezione dal manutentore (MAINTAINER) del file sorgente.

12