Home
last modified time | relevance | path

Searched full:repository (Results 1 – 25 of 702) sorted by relevance

12345678910>>...29

/openbmc/docs/
H A Dhw-vendor-repos-policy.md1 # Hardware Vendor Repository Policy
12 a request for a new repository or a bitbake recipe to be hosted under the
26 following requirements to be eligible for a repository under OpenBMC:
29 2. If an existing repository, it has an active maintainer
32 4. The new repository will not break others (i.e. providing new APIs utilized by
33 a common repository that are not protected by compile flags, etc)
37 - Reference: "Create a new repository" TOF [process][tof]
40 Note that the first option should always be to look into hosting the repository
41 under OpenBMC (vs. a recipe in OpenBMC that points to an external repository).
43 A repository must be hosted under OpenBMC if:
[all …]
H A Dmeta-layer-guidelines.md30 through a gerrit review, and follow the processes outlined for the repository.
92 bypass code review by pointing the upstream recipe to a public repository that
102 under the openbmc/openbmc repository where it can be reviewed, along with an
111 **What defines an OpenBMC specific repository?**
113 Generally an OpenBMC specific repository is something that does any of the
136 and/or discord. If the design would require a new repository, request one using
143 Repository branches can change at any time. Pointing to an autorev revision
153 Point SRCREV to a specific commit of the repository, and increase the revision
162 repository and there is distinct continuous-integration style testing on each
163 repository type. Having code in the meta-layer omits leveraging this CI
[all …]
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dmaint-appx.rst19 kernel repository (or tree) and accompanying Metadata in the
23 particular Yocto Project Linux kernel repository and use it to build
28 Linux kernel source repository and ``yocto-kernel-cache`` Git trees. For
37 how to set up a local Git repository of the Yocto Project Linux kernel
42 Once you have cloned the kernel Git repository and the cache of Metadata
44 in the repository using the following Git command::
50 "standard/beagleboard" branch of the Yocto Linux kernel repository and
51 the "yocto-4.12" branch of the ``yocto-kernel-cache`` repository::
60 Branches in the ``yocto-kernel-cache`` repository correspond to Yocto Linux
68 kernel, you need to examine the ``yocto-kernel-cache`` Git repository.
[all …]
/openbmc/openbmc/poky/documentation/overview-manual/
H A Ddevelopment-environment.rst151 repository for that particular item. Having a local Git repository of
160 repository, any supported BSP tarball, or Yocto Project tools. Unpacking
172 BSP repository and the Source Directory (i.e. ``poky``)
173 repository. For example, if you have checked out the "&DISTRO_NAME_NO_CAP;"
193 and extracting these files does not produce a local copy of a Git repository
233 repository. The development branch is the "upstream" repository from which
246 The Yocto Project ``poky`` Git repository also has an upstream
247 contribution Git repository named ``poky-contrib``. You can see all the
248 branches in this repository using the web interface of the
254 branches into the "master" branch of the Git repository.
[all …]
/openbmc/phosphor-logging/test/openpower-pels/
H A Drepository_test.cpp17 #include "extensions/openpower-pels/repository.hpp"
54 EXPECT_EQ(Repository::getPELFilename(0x12345678, date), in TEST_F()
57 EXPECT_EQ(Repository::getPELFilename(0xAABBCCDD, date), in TEST_F()
60 EXPECT_EQ(Repository::getPELFilename(0x3AFF1, date), in TEST_F()
63 EXPECT_EQ(Repository::getPELFilename(100, date), in TEST_F()
66 EXPECT_EQ(Repository::getPELFilename(0, date), "2030112813060708_00000000"); in TEST_F()
71 Repository repo{repoPath}; in TEST_F()
80 auto name = Repository::getPELFilename(pel->id(), ts); in TEST_F()
94 using pelID = Repository::LogID::Pel; in TEST_F()
95 using obmcID = Repository::LogID::Obmc; in TEST_F()
[all …]
/openbmc/openbmc-tools/
H A DREADME.md3 The goal of this repository is to collect the two-minute hacks you write to
9 ## Repository Rules
16 Then this repository aims to be the default destination for your otherwise
22 Please use gerrit for all patches to this repository:
24 - [Gerrit](https://gerrit.openbmc-project.xyz/) Repository
42 ## How you consume the repository
45 the repository to your PATH might be a bit of a dice-roll. We may also move or
/openbmc/phosphor-logging/extensions/openpower-pels/
H A Drepository.cpp16 #include "repository.hpp"
63 Repository::Repository(const std::filesystem::path& basePath, size_t repoSize, in Repository() function in openpower::pels::Repository
81 void Repository::restore() in restore()
162 std::string Repository::getPELFilename(uint32_t pelID, const BCDTime& time) in getPELFilename()
171 void Repository::add(std::unique_ptr<PEL>& pel) in add()
206 void Repository::write(const PEL& pel, const fs::path& path) in write()
238 std::optional<Repository::LogID> Repository::remove(const LogID& id) in remove()
250 "Removing PEL from repository, PEL ID = {PEL_ID}, BMC log ID = {BMC_ID}", in remove()
276 std::optional<std::vector<uint8_t>> Repository::getPELData(const LogID& id) in getPELData()
298 std::optional<sdbusplus::message::unix_fd> Repository::getPELFD(const LogID& id) in getPELFD()
[all …]
H A Drepository.hpp17 * @class Repository
21 class Repository class
117 * of different types in the repository.
135 Repository() = delete;
136 ~Repository() = default;
137 Repository(const Repository&) = default;
138 Repository& operator=(const Repository&) = delete;
139 Repository(Repository&&) = delete;
140 Repository& operator=(Repository&&) = delete;
145 * @param[in] basePath - the base filesystem path for the repository
[all …]
H A Dpel_entry.hpp13 class Repository;
31 * @param[in] repo - Repository pointer to lookup PEL to set appropriate
37 Repository* repo) : in PELEntry()
62 * @brief Repository pointer to look for updating PEL fields.
64 Repository* _repo;
/openbmc/openbmc-test-automation/tools/
H A Dgithub_issues_to_csv6 from a repository that username has access to. Supports GitHub API v3.
71 name Name of the GitHub repository
72 response GitHub repository response
100 description="Write GitHub repository issues to CSV file."
110 help="Repository names, formatted as 'basereponame/repo'",
130 for repository in args.repositories:
131 csvfilename_temp = "{}".format(repository.replace("/", "-"))
149 for repository in args.repositories:
151 l_url = l_url.format(repository, states)
154 get_issues_from_github_to_csv(repository, response)
/openbmc/docs/designs/
H A Dplatform-init.md37 Initially, a new repository would be created to house the platform-init for
54 Guard rails will need to evolve over time, but initially this repository will
66 1. Will require a new repository, recipe, and CI build.
71 - Does this proposal require a new repository? Yes Request for the repository is
73 - Who will be the initial maintainer(s) of this repository? Ed Tanous and
76 openbmc/openbmc New repository
/openbmc/qemu/.gitlab-ci.d/cirrus/
H A DREADME.rst14 builds to happen when you push to your GitLab repository, you need to
16 * set up a GitHub repository for the project, eg. ``yourusername/qemu``.
17 This repository needs to exist for cirrus-run to work, but it doesn't need to
34 repository, create two new variables:
36 * ``CIRRUS_GITHUB_REPO``, containing the name of the GitHub repository
48 repository as usual and you'll automatically get the additional CI coverage.
/openbmc/openbmc/poky/
H A DREADME.poky.md43 As Poky is an integration repository (built using a tool called combo-layer),
49 - Git repository: <https://git.openembedded.org/openembedded-core/>
54 - Git repository: <https://git.openembedded.org/bitbake/>
59 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/>
64 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto>
67 If in doubt, check the openembedded-core git repository for the content you
70 git repository branch in question.
H A DREADME.md43 As Poky is an integration repository (built using a tool called combo-layer),
49 - Git repository: <https://git.openembedded.org/openembedded-core/>
54 - Git repository: <https://git.openembedded.org/bitbake/>
59 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/>
64 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto>
67 If in doubt, check the openembedded-core git repository for the content you
70 git repository branch in question.
/openbmc/openbmc/poky/meta-poky/
H A DREADME.poky.md43 As Poky is an integration repository (built using a tool called combo-layer),
49 - Git repository: <https://git.openembedded.org/openembedded-core/>
54 - Git repository: <https://git.openembedded.org/bitbake/>
59 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/>
64 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto>
67 If in doubt, check the openembedded-core git repository for the content you
70 git repository branch in question.
/openbmc/docs/security/
H A Dhow-to-report-a-security-vulnerability.md18 - If you know which source code repository is affected, find the repository
28 separate owners. If you do not know which repository is affected, the owner or
32 security advisory][] in their repository and begin work. The advisory has draft
60 - If the problem is not severe, please write an issue to the affected repository
76 …https://docs.github.com/en/code-security/repository-security-advisories/creating-a-repository-secu…
/openbmc/openbmc-test-automation/ipmi/
H A Dtest_ipmi_inband_sdr.robot6 ... 3. Reserve Device SDR Repository,
175 Verify Reserve Device SDR Repository Via Inband IPMI
176 [Documentation] Verify Reserve Device SDR Repository via inband IPMI.
179 # Reserve Device SDR Repository via inband IPMI.
180 ${resp}= Get Reserve Device SDR Repository
188 Verify Reserve Device SDR Repository For Invalid Data Request
189 [Documentation] Verify Reserve Device SDR Repository via inband IPMI with extra request bytes.
192 # Reserve Device SDR Repository with extra request bytes.
200 Verify Reserve Device SDR Repository Info Via IPMI Lanplus
201 [Documentation] Verify whether Reserve Device SDR Repository command is accessible via lanplus.
[all …]
/openbmc/openbmc/poky/bitbake/lib/bb/fetch2/
H A Dgomod.py5 from a module proxy or directly from a version control repository.
32 The method used when fetching directly from a version control repository.
36 The URL when fetching directly from a version control repository. Required
41 repository. Alternatively, set the SRCREV varible for "module@version".
45 repository. Required when the module is not located in the root of the
46 repository.
163 """Class to fetch Go modules directly from a git repository"""
170 """Set up to download the module from the git repository.
172 Set up to download the git repository to the module cache directory and
175 cache/vcs/<hash>: The bare git repository.
[all …]
/openbmc/openpower-host-ipmi-oem/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
/openbmc/ibm-logging/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
/openbmc/pyphosphor/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
/openbmc/phosphor-state-manager/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
/openbmc/ibm-dbus-interfaces/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
/openbmc/phosphor-mrw-tools/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
/openbmc/phosphor-watchdog/
H A DOWNERS5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.

12345678910>>...29