Home
last modified time | relevance | path

Searched refs:Push (Results 1 – 14 of 14) sorted by relevance

/openbmc/libpldm/docs/checklists/
H A Dreleases.md27 - [ ] Push the release commit for review in Gerrit
30 - [ ] Push the release tag
/openbmc/u-boot/doc/SPI/
H A DREADME.sh_qspi_test36 #3, Push reset button.
/openbmc/openbmc/poky/meta/lib/oe/
H A Dpatch.py106 def Push(self, force): member in PatchSet
259 def Push(self, force = False, all = False, run = True): member in PatchTree
738 def Push(self, force = False, all = False, run = True): member in QuiltTree
817 self.patchset.Push()
838 self.patchset.Push(False)
841 patchcmd = self.patchset.Push(True, False, False)
/openbmc/docs/designs/
H A Dredfish-eventservice.md56 - For Push style event subscription creation, BMC shall respond to a successful
60 - For Push style event subscription creation, BMC shall respond to client with
94 1. Push style events (https): When the service detects the need to send an
160 Push style events(HTTPS) flow diagram:
460 2. Push style events(HTTP/HTTPS): It covers how to subscribe for Push style
618 subscription types such as 'Push style events' and 'SSE' and more detailed are
660 "DeliveryRetryIntervalSeconds". In case of Push Style Events if send fails due
691 file will be updated only for Push style event subscription information. SSE
832 ### Push style events (HTTP/HTTPS)
858 Example for created Push style event is documented in testing section of same
[all …]
/openbmc/docs/development/
H A Dgerrit-setup.md94 ### Push Code Change to Gerrit
106 - Push your changes to Gerrit for code review:
/openbmc/openbmc/poky/meta/recipes-core/libxml/
H A Dlibxml2_2.14.3.bb2 DESCRIPTION = "The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push a…
/openbmc/u-boot/arch/arm/dts/
H A Dam3517-evm.dts44 label = "User Push Button";
/openbmc/qemu/target/arm/tcg/
H A Dt16.decode250 # Push and Pop
/openbmc/webui-vue/
H A DCONTRIBUTING.md149 1. Push your changes to Gerrit for code review:
/openbmc/qemu/docs/interop/
H A Dbitmaps.rst534 Incremental Backups - Push Model
541 The "Push Model" here references the fact that QEMU is "pushing" the modified
881 Example: Incremental Push Backups without Backing Files
1192 Push Backup Errors & Recovery
1219 Incremental Push Backup jobs that fail individually behave simply as
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Dsubmit-changes.rst564 Using Scripts to Push a Change Upstream and Request a Pull
585 #. *Request Push Access to an "Upstream" Contrib Repository:* Send an email to
595 #. *Push Your Commits to the "Contrib" Upstream:* Push your
/openbmc/u-boot/arch/arm/mach-sunxi/
H A DKconfig55 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
/openbmc/openbmc/poky/documentation/overview-manual/
H A Ddevelopment-environment.rst329 - *Use Push and Pull:* The push-pull workflow is based on the concept
/openbmc/qemu/tcg/aarch64/
H A Dtcg-target.c.inc3449 /* Push (FP, LR) and allocate space for all saved registers. */