Home
last modified time | relevance | path

Searched refs:stable (Results 1 – 25 of 49) sorted by relevance

12

/f-stack/dpdk/doc/guides/contributing/
H A Dstable.rst18 consumers of DPDK with a stable target on which to base applications or
37 The duration of a stable is one complete release cycle (3 months). It can be
38 longer, up to 1 year, if a maintainer continues to support the stable branch,
50 A stable release can be designated as an LTS release based on community
55 https://git.dpdk.org/dpdk-stable where bugfixes will be backported to.
66 For a list of the currently maintained stable/LTS branches please see
67 the latest `stable roadmap <https://core.dpdk.org/roadmap/#stable>`_.
77 branch with a Fixes: tag should be backported to the relevant stable/LTS
89 Cc: stable@dpdk.org
108 The Stable and LTS release are coordinated on the stable@dpdk.org mailing
[all …]
H A Dindex.rst18 stable
H A Dvulnerability.rst10 Only the main repositories (dpdk and dpdk-stable) of the core project
12 If a stable branch is declared unmaintained (end of life),
280 * For long and short term stable branches fixed,
292 and `stable@dpdk.org <mailto:stable@dpdk.org>`_ accordingly.
H A Dpatches.rst324 should also be CCed to the `stable@dpdk.org <https://mails.dpdk.org/listinfo/stable>`_
326 In the commit message body the Cc: stable@dpdk.org should be inserted as follows::
333 Cc: stable@dpdk.org
337 For further information on stable contribution you can go to
338 :doc:`Stable Contribution Guide <stable>`.
549 for a stable release rather than mainline.
550 In this case the patch(es) should be sent to ``stable@dpdk.org``,
553 Given that there are multiple stable releases being maintained at the same time,
H A Dabi_versioning.rst48 **single ABI version**. In addition, the need to maintain a stable ABI for some
121 DPDK versions being installed alongside each other. Both stable and
160 The macro is used when a symbol matures to become part of the stable ABI, to
429 In situations in which an ``experimental`` symbol has been stable for some time,
430 and it becomes a candidate for promotion to the stable ABI. At this time, when
472 When we promote the symbol to the stable ABI, we simply strip the
/f-stack/dpdk/devtools/
H A Dgit-log-fixes.sh110 stable=$(stable_tag $id)
112 [ "$stable" = "S" ] || [ "$fixes" = "F" ] || [ -n "$origins" ] || \
123 printf '%s %7s %s %s %s (%s)\n' $version $id $stable $fixes "$headline" "$origver"
/f-stack/freebsd/contrib/device-tree/Bindings/
H A DABI.rst7 I. Regarding stable bindings/ABI, we quote from the 2013 ARM mini-summit
10 "That still leaves the question of, what does a stable binding look
11 like? Certainly a stable binding means that a newer kernel will not
/f-stack/freebsd/contrib/device-tree/Bindings/sound/
H A Dcs4271.txt24 The CS4271 requires its LRCLK and MCLK to be stable before its RESET
33 Note that this is not needed in case the clocks are stable
/f-stack/freebsd/contrib/openzfs/contrib/pyzfs/
H A DREADME3 libzfs_core is intended to be a stable interface for programmatic
20 do reach stable storage. That means that the operations are done
/f-stack/freebsd/contrib/device-tree/Bindings/net/dsa/
H A Dmarvell.txt5 FLASH never to be changed again. Once this binding is stable, this
8 If you need a stable binding, use the old dsa.txt binding.
/f-stack/freebsd/contrib/openzfs/contrib/intel_qat/patch/
H A D0001-cryptohash.diff2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=228c4f265c6eb60eaa4ed0e…
H A D0001-pci_aer.diff4 git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=894020fdd88c1e9a74c60b67c0f19f1…
/f-stack/app/redis-5.0.5/deps/jemalloc/include/jemalloc/
H A Djemalloc_mangle.sh29 * The ${symbol_prefix}* macros can be used as stable alternative names for the
/f-stack/freebsd/contrib/device-tree/Bindings/input/
H A Dmatrix-keymap.yaml14 defining the keys in the scope of linux key codes since that is a stable and
H A Drotary-encoder.txt17 - rotary-encoder,steps-per-period: Number of steps (stable states) per period.
H A Dmicrochip,qt1050.txt5 functions necessary to provide stable sensing under a wide variety of changing
/f-stack/freebsd/contrib/zstd/
H A DCONTRIBUTING.md177 Unfortunately, the most important aspect in being able to benchmark reliably is to have a stable
179 will typically not be stable enough to obtain reliable benchmark results. If you can get your
182 Of course, benchmarking can be done on non-hyper-stable machines as well. You will just have to
184 noise. Here are some things you can do to make your benchmarks more stable:
192 results. While this is certainly going to be a more stable number than a raw single sample
197 with the fastest running time) has been the most stable approach.
198 * The more samples you have, the more stable your benchmarks should be. You can verify
213 on Windows. You will get more stable benchmark results of you end those processes as well.
222 definitely some). Statically linking libzstd will be more stable. Static libraries should
243 Usually, the longer the running time, the more stable your results will be.
/f-stack/freebsd/contrib/device-tree/Bindings/mmc/
H A Darasan,sdhci.txt61 - xlnx,int-clock-stable-broken: when present, the controller always reports
62 that the internal clock is stable even when it is not.
H A Darasan,sdhci.yaml142 xlnx,int-clock-stable-broken:
146 is stable even when it is not.
/f-stack/freebsd/contrib/device-tree/Bindings/display/exynos/
H A Dexynos_hdmi.txt30 parents i.e. sclk_pixel and sclk_hdmiphy. If hdmiphy is stable
/f-stack/freebsd/contrib/device-tree/Bindings/arm/
H A Dsyna.txt17 stable binding/ABI.
H A Damlogic.yaml21 stable binding/ABI.
/f-stack/freebsd/contrib/device-tree/Bindings/gpio/
H A Dgpio-eic-sprd.txt12 stable status (millisecond resolution) and a single-trigger mechanism
/f-stack/freebsd/contrib/device-tree/Bindings/cpufreq/
H A Dcpufreq-mediatek.txt10 transition and not stable yet.
/f-stack/freebsd/contrib/openzfs/module/lua/
H A DREADME.zfs35 The Lua runtime is considered stable software. Channel programs don't need much

12