Home
last modified time | relevance | path

Searched full:upstream (Results 1 – 25 of 3793) sorted by relevance

12345678910>>...152

/openbmc/docs/
H A Dkernel-development.md4 general development policy is that code must be upstream first. This is a strong
10 carried, as everything should be upstream.
15 1. When the OpenBMC kernel moves to a new upstream release
16 2. By backporting upstream commits from a newer kernel version to the OpenBMC
24 1. Submit your patch upstream. It doesn't need to be upstream, but it should be
32 When developing a new driver, your goal is to have the code accepted upstream.
34 hardware you wish to support. Check the OpenBMC `-dev` tree, check upstream, and
38 driver, before sending it upstream to the relevant maintainers. You should feel
39 welcome to cc the OpenBMC list when sending upstream, so other kernel developers
40 can provide input where appropriate. Be sure to follow the (upstream development
[all …]
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Drecipe-style-guide.rst28 revisions that upstream are expecting people to use.
65 that reference the same upstream source version. It can be used to force a
129 - :term:`SUMMARY`: a one line description of the upstream project
131 - :term:`DESCRIPTION`: an extended description of the upstream project,
135 - :term:`HOMEPAGE`: the URL to the upstream projects homepage.
137 - :term:`BUGTRACKER`: the URL upstream projects bug tracking website,
263 try to link to upstream making/justifying that decision.
286 Patch Upstream Status
291 requires information about the upstream status of each patch.
297 Then, you should also add an ``Upstream-Status:`` tag containing one of the
[all …]
/openbmc/openbmc/poky/bitbake/lib/prserv/
H A Dserv.py83 # We have an upstream server.
86 # depend on what's on the upstream server. That's why we're calling find_value()
101 # and is at least greater than the maximum upstream value
109 # Ask upstream whether it knows the checksum
112 # Upstream doesn't have our checksum, let create a new one
115 # Fine to take the same value as upstream
124 # Let's ask the upstream server whether it knows it
130 # The package is not known upstream, must be a local-only package
136 # The package is known upstream, let's ask the upstream server
143 # Upstream knows this output hash, let's store it and use it too.
[all …]
H A Dtests.py49 def start_server(self, name, dbfile, upstream=None, read_only=False, prefunc=server_prefunc): argument
59 upstream=upstream,
273 self.server1 = self.start_server("upstream1", dbfile1, upstream=self.server2.address)
277 self.server0 = self.start_server("local", dbfile0, upstream=self.server1.address)
289 … self.assertEqual(result, "0", "getPR: initial PR of a package should be '0' (same as upstream)")
292 … self.assertEqual(result, "0", "getPR: initial PR of a package should be '0' (same as upstream)")
297 …ult, "0.0", "getPR: first PR of a package which has a different checksum upstream should be '0.0'")
300 …ult, "0.1", "getPR: second PR of a package that has a different checksum upstream should be '0.1'")
314 …self.assertEqual(result, "0.3.0", "getPR: first PR of a package that doesn't exist upstream should…
317 …qual(result, "0.3.1", "getPR: second PR of a package that doesn't exist upstream should be '0.3.1'…
[all …]
/openbmc/linux/Documentation/process/
H A Dcontribution-maturity-model.rst19 take on upstream contributions such as reviewing other people’s patches,
24 expectations for upstream community engagement aim to increase the
35 upstream community.
58 * A Software Engineer’s upstream code contributions will be considered
78 * The number of upstream kernel contributions by team or organization
80 * The percentage of kernel developers who have made upstream
84 and/or products, and the publication date of the upstream kernel
92 time focused on Upstream Work, which is defined as reviewing patches,
94 such as writing or maintaining tests, upstream tech debt reduction,
104 * Upstream kernel development is considered a formal job position, with
[all …]
/openbmc/linux/rust/alloc/
H A DREADME.md9 upstream. In general, only additions should be performed (e.g. new
10 methods). Eventually, changes should make it into upstream so that,
13 The Rust upstream version on top of which these files are based matches
24 upstream as possible and avoid as much divergence as possible, which
28 in-tree that would be as small and as close as possible to upstream.
29 Then, upstream can start adding the functions that we add to `alloc`
32 upstream, so that we can drop `alloc` from the kernel tree and go back
33 to using the upstream one.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/tinyproxy/tinyproxy/
H A Dtinyproxy.conf134 # Upstream:
136 # Turns on upstream proxy support.
138 # The upstream rules allow you to selectively route upstream connections
143 # upstream testproxy:8008 ".test.domain.invalid"
144 # upstream testproxy:8008 ".our_testbed.example.com"
145 # upstream testproxy:8008 "192.168.128.0/255.255.254.0"
147 # # no upstream proxy for internal websites and unqualified hosts
148 # no upstream ".internal.example.com"
149 # no upstream "www.example.com"
150 # no upstream "10.0.0.0/8"
[all …]
/openbmc/openbmc/meta-arm/ci/
H A Dpatchreview29 # Whether the patch has an Upstream-Status or not
31 # If the Upstream-Status tag is malformed in some way (string for bad bit)
33 # If the Upstream-Status value is unknown (boolean)
35 # The upstream status value (Pending, etc)
71 … status_re = re.compile(r"^[\t ]*(Upstream[-_ ]Status:?)[\t ]*(\w*)", re.IGNORECASE | re.MULTILINE)
94 # Find the Upstream-Status tag
98 if value != "Upstream-Status:":
167 print("Missing Upstream-Status tag (%s)" % patch)
171 print("Malformed Upstream-Status '%s' (%s)" % (r.malformed_upstream_status, patch))
175 print("Unknown Upstream-Status value '%s' (%s)" % (r.upstream_status, patch))
[all …]
/openbmc/openbmc/poky/meta/conf/distro/include/
H A Dcve-extra-exclusions.inc19 CVE_STATUS[CVE-2000-0006] = "upstream-wontfix: cpe:*:strace: CVE is more than 20 years old \
23 CVE_STATUS[CVE-2005-0238] = "upstream-wontfix: cpe:*:epiphany: \
31 CVE_STATUS[CVE-2010-4756] = "upstream-wontfix: cpe:*:glibc: \
34 Upstream don't see it as a security issue, ftp servers shouldn't be passing \
35 this to libc glob. Upstream have no plans to add BSD's GLOB_LIMIT or similar."
53 CVE_STATUS_DB[status] = "upstream-wontfix: cpe:*:berkeley_db: Since Oracle relicensed bdb, the open…
69 CVE_STATUS[CVE-2021-20255] = "upstream-wontfix: cpe:*:qemu: \
75 CVE_STATUS[CVE-2019-12067] = "upstream-wontfix: cpe:*:qemu: \
76 There was a proposed patch but rejected by upstream qemu. It is unclear if the issue can \
78 We'll pick up any fix when upstream accepts one."
[all …]
/openbmc/openbmc/poky/meta/recipes-support/libyaml/
H A Dlibyaml_0.2.5.bb21 CVE_STATUS[CVE-2024-35325] = "upstream-wontfix: Upstream thinks this is a misuse (or wrong use) of …
22 CVE_STATUS[CVE-2024-35326] = "upstream-wontfix: Upstream thinks there is no working code that is ex…
23 CVE_STATUS[CVE-2024-35328] = "upstream-wontfix: Upstream thinks there is no working code that is ex…
/openbmc/linux/Documentation/translations/sp_SP/process/
H A Dcontribution-maturity-model.rst24 upstream, como revisar los parches de otras personas, reestructurar la
29 expectativas comunes para la participación con la comunidad upstream
41 upstream.
63 * Las contribuciones de código upstream de un ingeniero de software se
84 * El número de contribuciones al kernel upstream por equipo u
88 contribuciones upstream relativo al total de desarrolladores
92 upstream en el que se basa el kernel interno.
103 de tecnología upstream, escribir documentación, etc.
112 * El desarrollo del kernel upstream se considera un puesto de trabajo
119 de trabajo upstream a trabajo enfocado en perseguir directamente los
/openbmc/openbmc/poky/meta/lib/patchtest/tests/
H A Dtest_patch.py33 self.standard_format = "Upstream-Status: <Valid status>"
44 … self.skip("There are no new software patches, no reason to test Upstream-Status presence/format")
50 … "Added patch file is missing Upstream-Status: <Valid status> in the commit message",
67 "Upstream-Status is Inappropriate, but no reason was provided",
72 "Upstream-Status: Inappropriate [reason]",
83 "Upstream-Status is Submitted, but it is not mentioned where",
88 "Upstream-Status: Submitted [where]",
97 "Upstream-Status is in incorrect format",
/openbmc/openbmc/poky/scripts/contrib/
H A Dpatchreview.py26 … = ("accepted", "pending", "inappropriate", "backport", "submitted", "denied", "inactive-upstream")
29 # Whether the patch has an Upstream-Status or not
31 # If the Upstream-Status tag is malformed in some way (string for bad bit)
33 # If the Upstream-Status value is unknown (boolean)
35 # The upstream status value (Pending, etc)
62 …status_re = re.compile(r"^[\t ]*(Upstream[-_ ]Status:?)[\t ]*([\w-]*)", re.IGNORECASE | re.MULTILI…
85 # Find the Upstream-Status tag
164 print("Missing Upstream-Status tag (%s)" % patch)
168 print("Malformed Upstream-Status '%s' (%s)" % (r.malformed_upstream_status, patch))
172 print("Unknown Upstream-Status value '%s' (%s)" % (r.upstream_status, patch))
[all …]
/openbmc/linux/Documentation/maintainer/
H A Drebasing-and-merging.rst68 newer base or avoiding a merge with an upstream repository is not
102 required before any given branch finds its way into an upstream repository.
127 requests, and upstream maintainers should verify the tags when pulling
135 Merging from sibling or upstream trees
139 trees tend to be a red flag when it comes time to push a branch upstream.
152 you are managing is stable and ready for upstream. Frequent merges can
160 Even then, you should not back merge a tree above your immediate upstream
161 tree; if a higher-level back merge is really required, the upstream tree
165 maintainer merges with the upstream in order to resolve merge conflicts
185 asking upstream to do.
[all …]
/openbmc/pldm/oem/ibm/libpldmresponder/
H A Dfile_io.cpp44 uint32_t upstream; //!< boolean indicating the direction of the DMA member
94 xdmaOp.upstream = 0; in transferHostDataToSocket()
123 uint64_t address, bool upstream) in transferDataHost() argument
161 vgaMem = mmap(nullptr, pageAlignedLength, upstream ? PROT_WRITE : PROT_READ, in transferDataHost()
174 if (upstream) in transferDataHost()
180 …fer data between BMC and remote terminus due to lseek failure with upstream '{UPSTREAM}' at offset… in transferDataHost()
181 "ERROR_NUM", errno, "UPSTREAM", upstream, "OFFSET", offset); in transferDataHost()
194 …to transfer data between BMC and remote terminus with file read on upstream '{UPSTREAM}' of length… in transferDataHost()
195 "ERROR_NUM", errno, "UPSTREAM", upstream, "LENGTH", length, in transferDataHost()
202 …and remote terminus mismatched for number of characters to read on upstream '{UPSTREAM}' and the l… in transferDataHost()
[all …]
H A Dfile_io_by_type.cpp34 int FileHandler::transferFileData(int32_t fd, bool upstream, uint32_t offset, in transferFileData() argument
41 address, upstream); in transferFileData()
51 xdmaInterface.transferDataHost(fd, offset, length, address, upstream); in transferFileData()
74 int FileHandler::transferFileData(const fs::path& path, bool upstream, in transferFileData() argument
79 if (upstream) in transferFileData()
103 if (upstream) in transferFileData()
123 return transferFileData(fd(), upstream, offset, length, address); in transferFileData()
/openbmc/linux/drivers/net/phy/
H A Dsfp-bus.c28 void *upstream; member
464 ops->link_down(bus->upstream); in sfp_register_bus()
466 ret = ops->connect_phy(bus->upstream, bus->phydev); in sfp_register_bus()
475 bus->upstream_ops->attach(bus->upstream, bus); in sfp_register_bus()
484 bus->upstream_ops->detach(bus->upstream, bus); in sfp_unregister_bus()
489 ops->disconnect_phy(bus->upstream); in sfp_unregister_bus()
585 bus->upstream = NULL; in sfp_upstream_clear()
624 * - an error from the upstream's connect_phy() method.
656 * @upstream: the upstream private data
657 * @ops: the upstream's &struct sfp_upstream_ops
[all …]
/openbmc/openbmc/poky/documentation/overview-manual/
H A Ddevelopment-environment.rst169 to create a local copy of the upstream repositories.
187 For steps on how to view and access these upstream Git repositories,
233 repository. The development branch is the "upstream" repository from which
246 The Yocto Project ``poky`` Git repository also has an upstream
257 maintain cloned repositories of upstream branches. The cloned
264 with whatever upstream branch they are working against. They are also
272 maintainer include them into an upstream branch. This process is called
334 pull changes submitted by other developers from the upstream
341 …":ref:`contributor-guide/submit-changes:using scripts to push a change upstream and request a pull…
425 development branch from the upstream source Git repository. In other
[all …]
/openbmc/openbmc/poky/meta/conf/
H A Dcve-check-map.conf7 # use when NVD DB does not mention patched versions of stable/LTS branches which have upstream CVE …
18 # use when CVE is confirmed by upstream but fix is still not available
27 # use when upstream does not accept the report as a vulnerability (e.g. works as designed)
33 # use when upstream acknowledged the vulnerability but does not plan to fix it
34 CVE_CHECK_STATUSMAP[upstream-wontfix] = "Ignored"
/openbmc/entity-manager/src/
H A Dtopology.cpp50 // look at each upstream port type in getAssocs()
61 for (const Path& upstream : upstreamPortPair.second) in getAssocs() local
63 if (boardTypes[upstream] == "Chassis" || in getAssocs()
64 boardTypes[upstream] == "Board") in getAssocs()
72 "containing", upstream); in getAssocs()
75 result[upstream].emplace_back( in getAssocs()
/openbmc/openbmc/poky/meta/recipes-devtools/perl-cross/files/
H A Ddeterminism.patch8 Reported upstream: https://github.com/arsv/perl-cross/issues/87
12 Reported upstream: https://github.com/arsv/perl-cross/issues/88
16 This needs to go to upstream perl (not done)
20 Reported upstream: https://github.com/arsv/perl-cross/issues/87
24 Upstream-Status: Pending [75% submitted]
/openbmc/linux/drivers/fsi/
H A Dfsi-master-hub.c29 * device (the hub->upstream device), and provides access to the downstream FSI
38 struct fsi_device *upstream; member
54 return fsi_slave_read(hub->upstream->slave, addr, val, size); in hub_master_read()
66 return fsi_slave_write(hub->upstream->slave, addr, val, size); in hub_master_write()
94 return fsi_device_write(hub->upstream, FSI_MCENP0 + (4 * idx), in hub_master_link_enable()
97 rc = fsi_device_write(hub->upstream, FSI_MSENP0 + (4 * idx), &reg, 4); in hub_master_link_enable()
126 struct fsi_device *dev = hub->upstream; in hub_master_init()
226 hub->upstream = fsi_dev; in hub_master_probe()
267 fsi_slave_release_range(hub->upstream->slave, hub->addr, hub->size); in hub_master_remove()
/openbmc/openbmc/poky/meta/recipes-devtools/perl/files/
H A Ddeterminism.patch8 Reported upstream: https://github.com/arsv/perl-cross/issues/87
12 Reported upstream: https://github.com/arsv/perl-cross/issues/88
16 Submitted to upstream perl: https://github.com/dankogai/p5-encode/pull/179
20 Reported upstream: https://github.com/arsv/perl-cross/issues/87
24 Upstream-Status: Submitted [see links above]
/openbmc/u-boot/tools/patman/
H A Dgitutil.py62 pipe = [LogCmd('@{upstream}..', oneline=True),
85 """Tries to guess the upstream for a branch
88 upstream. It does this by looking for the first commit where
97 Name of upstream branch (e.g. 'upstream/master') or None if none
111 return name, "Guessing upstream as '%s'" % name
112 return None, "Cannot find a suitable upstream for branch '%s'" % branch
115 """Returns the name of the upstream for a branch
123 Name of upstream branch (e.g. 'upstream/master') or None if none
132 upstream, msg = GuessUpstream(git_dir, branch)
133 return upstream, msg
[all …]
/openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/
H A Ddistrodata.py15 Summary: Test that upstream version checks do not regress
16 …Expected: Upstream version checks should succeed except for the recipes listed in the exception…
30 The following packages failed upstream version checks. Please fix them using UPSTREAM_CHECK_URI/UPS…
31 (when using tarballs) or UPSTREAM_CHECK_GITTAGREGEX (when using git). If an upstream version check …
32 (for example, if upstream does not use git tags), you can set UPSTREAM_VERSION_UNKNOWN to '1' in th…
37 The following packages have been checked successfully for upstream versions,

12345678910>>...152