Home
last modified time | relevance | path

Searched refs:Pull (Results 1 – 25 of 38) sorted by relevance

12

/Zephyr-latest/.github/ISSUE_TEMPLATE/
D008_bin-blobs.md28 ## Pull Request
30 Link to the Pull request with the actual implementation of the integration. If
31 you are submitting this as part of a new module you may link to the same Pull
D007_ext-source.md31 ## Pull Request
33 Pull request (if any) with the actual implementation of the integration, be it
/Zephyr-latest/subsys/net/lib/prometheus/
DKconfig5 bool "Prometheus Client Library (Pull Method)"
/Zephyr-latest/doc/develop/api/
Dapi_lifecycle.rst104 #. A Pull Request must be opened that changes the corresponding entry in the
108 #. The Pull Request must be submitted for discussion in the next
109 `Zephyr Architecture meeting`_ where, barring any objections, the Pull Request
155 Pull Request containing those changes in code form.
166 Finally, and if not done as part of the first step, a Pull Request must be
168 whether to introduce both the RFC and the Pull Request at the same time or to
171 The Pull Request must include the following:
193 depend on the approval of the actual Pull Request by the maintainer of the
194 corresponding subsystem. As with any other Pull Request, the author can request
197 If the Pull Request is merged then an email must be sent to the ``devel`` and
/Zephyr-latest/doc/project/
Ddev_env_and_tools.rst10 is accepted into the code base. Changes, in the form of Pull Requests (PR) are
17 Pull requests should be appropriately :ref:`labeled<gh_labels>`,
49 :alt: Pull request classes
52 Pull request classes
108 A Pull-Request should have an Assignee
117 - Pull requests should not be merged without an approval by the assignee.
119 Pull Request should not be merged by author without review
142 - Assign Pull Request to yourself, this will mean that a pull request should
146 Pull Requests should have at least 2 approvals before they are merged
175 Closing Stale Issues and Pull Requests
[all …]
Dindex.rst25 **Pull Requests** (PRs) for submitting and reviewing changes. Zephyr
/Zephyr-latest/drivers/gpio/
Dgpio_stm32.c176 static inline void ll_gpio_set_pin_pull(GPIO_TypeDef *GPIOx, uint32_t Pin, uint32_t Pull) in ll_gpio_set_pin_pull() argument
184 if (Pull == LL_GPIO_PULL_UP) { in ll_gpio_set_pin_pull()
187 } else if (Pull == LL_GPIO_PULL_DOWN) { in ll_gpio_set_pin_pull()
190 } else if (Pull == LL_GPIO_PULL_NO) { in ll_gpio_set_pin_pull()
195 LL_GPIO_SetPinPull(GPIOx, Pin, Pull); in ll_gpio_set_pin_pull()
/Zephyr-latest/samples/boards/renesas/comparator/
DREADME.rst40 * Case 1: IVCMP3 connected to SW0 (Pull up)
/Zephyr-latest/samples/sensor/bmi270/
DREADME.rst24 Depending on the baseboard used, the **SDA** and **SCL** lines require Pull-Up
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob.rst80 When operating in Pull BLOB Transfer Mode, the BLOB Transfer Server will request a small number of
152 BLOBs can be transferred using two transfer modes, Push BLOB Transfer Mode and Pull BLOB Transfer
159 In Pull BLOB Transfer Mode, the BLOB Transfer Server will "pull" the chunks from the BLOB Transfer
160 Client at its own rate. Pull BLOB Transfer Mode can be conducted with multiple Target nodes, and is
162 in Pull BLOB Transfer Mode, the BLOB Transfer Server will request chunks from the BLOB Transfer
Dblob_cli.rst7 sending BLOBs of any size to any number of Target nodes, in both Push BLOB Transfer Mode and Pull
/Zephyr-latest/scripts/ci/
Dtwister_ignore.txt4 # changed in a patch series (Pull Request) and if all files in the pull request
/Zephyr-latest/samples/sensor/sht3xd/
DREADME.rst26 Depending on the baseboard used, the **SDA** and **SCL** lines require Pull-Up
/Zephyr-latest/
DCONTRIBUTING.rst32 * A Continuous Integration (CI) system runs on every Pull Request (PR)
/Zephyr-latest/samples/sensor/adt7420/
DREADME.rst31 Depending on the baseboard used, the **SDA** and **SCL** lines require Pull-Up
/Zephyr-latest/boards/adi/max78002evkit/doc/
Dindex.rst297 | | | | Open | | | Pull-up disabled, allowing port pin to be repu…
304 | | | | Open | | | Pull-up disabled, allowing port pin to be repu…
416 | | | | Open | | | Pull jumper if using AIN2 …
430 | | | | Open | | | Pull jumper if using AIN4 …
437 | | | | Open | | | Pull jumper if using AIN5 …
/Zephyr-latest/doc/services/net_buf/
Dindex.rst105 Pull
119 whereas the Remove and Pull operations are used when decoding data from a
/Zephyr-latest/samples/sensor/sgp40_sht4x/
DREADME.rst36 Depending on the baseboard used, the **SDA** and **SCL** lines require Pull-Up
/Zephyr-latest/doc/contribute/
Dguidelines.rst38 your Pull Request (PR). You can see any failure results in the workflow
293 Pull Requests and Issues
349 Pull Request Guidelines
351 When opening a new Pull Request, adhere to the following guidelines to ensure
354 If in doubt, it's advisible to explore existing Pull Requests within the Zephyr
492 change addresses a specific GitHub issue, include in the Pull Request message a
520 every Pull Request (PR) in order to verify several aspects of the PR:
529 checks have passed" before the Pull Request can be merged. CI is run when the
563 before opening a new Pull Request:
815 Pull Requests. If you follow them, chances are your pull request will get the
Dproposals_and_rfcs.rst62 As with Pull Requests, RFCs might require discussion in the context of one of
Dexternal.rst178 TSC to assess the merit of the request. Optionally you can also create a Pull
250 The TSC must approve every Pull Request that introduces a new external tooling
Dbin_blobs.rst224 both CI ran when a new GitHub Pull Request is opened as well as any other
249 TSC to assess the merit of the request. Additionally you must also create a Pull
/Zephyr-latest/doc/safety/
Dsafety_requirements.rst80 Pull Request requirement repository
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst88 | | - Pull: NONE | | - Pull: NONE |
92 | | - Pull: UP | | - Pull: NONE |
/Zephyr-latest/doc/releases/
Dindex.rst122 as well as refer to the Pull Request that introduced it, in order for the user

12