Searched full:stable (Results 1 – 25 of 1202) sorted by relevance
12345678910>>...49
... libevent-2.1.12-stable/ libevent-2.1.12-stable/util-internal.h ...
5 ….bootlin.com/downloads/releases/toolchains/aarch64/tarballs/aarch64--glibc--stable-2020.08-1.sha2566 sha256 8ab7a2f17cb96621b048ab0a872650dd62faa54cd74c961b9902b8c04bff7dd1 aarch64--glibc--stable-20…9 …s.bootlin.com/downloads/releases/toolchains/aarch64/tarballs/aarch64--musl--stable-2020.08-1.sha25610 sha256 8319d27e3e637f32ecbdf49ceee2e9b7768b32d3ec7c92c888ff52e6f062bde4 aarch64--musl--stable-202…13 …bootlin.com/downloads/releases/toolchains/aarch64/tarballs/aarch64--uclibc--stable-2020.08-1.sha25614 sha256 04176f56ac977215c5257c307cece2d32e03770b96380e09c50379d4d84a5b39 aarch64--uclibc--stable-2…17 …tlin.com/downloads/releases/toolchains/aarch64be/tarballs/aarch64be--glibc--stable-2020.08-1.sha25618 sha256 71e24a2a205726d7d8ec56ead13b7eb427d5aed0e057a94ee06688334a07e6dd aarch64be--glibc--stable-…21 …lin.com/downloads/releases/toolchains/aarch64be/tarballs/aarch64be--uclibc--stable-2020.08-1.sha25622 sha256 a3bff78e98b2e17ab142ec630f9184f0cd4be6f1f313fdc112d89a843d92cedc aarch64be--uclibc--stable…[all …]
81 bool "aarch64 glibc stable 2020.08-1"99 glibc C library. This is a stable version, which means it100 is using stable and proven versions of gcc, gdb and129 bool "aarch64 musl stable 2020.08-1"145 musl C library. This is a stable version, which means it is146 using stable and proven versions of gcc, gdb and binutils.174 bool "aarch64 uclibc stable 2020.08-1"190 uclibc C library. This is a stable version, which means it191 is using stable and proven versions of gcc, gdb and222 bool "aarch64be glibc stable 2020.08-1"[all …]
17 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = aarch64--glibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION).ta…29 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = aarch64--musl--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION).tar…41 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = aarch64--uclibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION).t…53 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = aarch64be--glibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION).…65 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = aarch64be--uclibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION)…77 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = arcle-750d--uclibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION…89 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = arcle-hs38--glibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION)…101 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = arcle-hs38--uclibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION…113 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = armv5-eabi--glibc--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION)…125 TOOLCHAIN_EXTERNAL_BOOTLIN_SOURCE = armv5-eabi--musl--stable-$(TOOLCHAIN_EXTERNAL_BOOTLIN_VERSION).…[all …]
3 Everything you ever wanted to know about Linux -stable releases7 "-stable" tree:35 Procedure for submitting patches to the -stable tree38 - Security patches should not be handled (solely) by the -stable review50 To have the patch automatically included in the stable tree, add the tag54 Cc: stable@vger.kernel.org57 the stable tree without anything else needing to be done by the author66 stable@vger.kernel.org containing the subject of the patch, the commit ID,76 stable@vger.kernel.org. You must note the upstream commit ID in the104 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle[all …]
11 kernel interface, nor does it have a stable kernel interface**.19 the syscall interface. That interface is **very** stable over time, and23 on being stable.28 You think you want a stable kernel interface, but you really do not, and29 you don't even know it. What you want is a stable running driver, and32 tree, all of which has made Linux into such a strong, stable, and mature53 So, there are two main topics here, binary kernel interfaces and stable60 Assuming that we had a stable kernel source interface for the kernel, a101 Stable Kernel Source Interfaces140 stable source interface, a new interface would have been created, and
248 The 5.x.y (-stable) and 5.x patches live at257 The stable -rc patches live at259 https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/265 These are the base stable releases released by Linus. The highest numbered268 If regressions or other serious flaws are found, then a -stable fix patch300 Kernels with 3-digit versions are -stable kernels. They contain small(ish)304 This is the recommended branch for users who want the most recent stable309 the current stable kernel.313 The -stable team usually do make incremental patches available as well341 These kernels are not stable and you should expect occasional breakage if[all …]
38 deemed to be sufficiently stable (and which is accepted by the development70 considered to be sufficiently stable and the final release is made.77 September 15 5.3 stable release86 November 24 5.4 stable release90 the stable release? The most significant metric used is the list of97 The developers' goal is to fix all known regressions before the stable106 Once a stable release is made, its ongoing maintenance is passed off to the107 "stable team," currently Greg Kroah-Hartman. The stable team will release108 occasional updates to the stable release using the 5.x.y numbering scheme.111 kernel. Kernels will typically receive stable updates for a little more[all …]
128 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`130 not have a stable API within the kernel, including things like:153 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`154 This file describes the rules on how the stable kernel releases239 - Various stable trees with multiple major numbers279 Various stable trees with multiple major numbers282 Kernels with 3-part versions are -stable kernels. They contain285 in a major stable series increments the third part of the version288 This is the recommended branch for users who want the most recent stable292 Stable trees are maintained by the "stable" team <stable@vger.kernel.org>, and[all …]
2 This is Japanese translated version of "Documentation/process/stable-kernel-rules.rst".15 linux-2.6.29/Documentation/process/stable-kernel-rules.rst28 ずっと知りたかった Linux 2.6 -stable リリースの全て30 "-stable" ツリーにどのような種類のパッチが受け入れられるか、どのような48 Linus のツリーでのコミットID を -stable へのパッチ投稿の際に引用す51 -stable ツリーにパッチを送付する手続き-53 - 上記の規則に従っているかを確認した後に、stable@vger.kernel.org にパッチ59 メンテナーによるレビューのために -stable キューに追加される。60 - パッチに stable@vger.kernel.org のアドレスが付加されているときには、それ61 が Linus のツリーに入る時に自動的に stable チームに email される。[all …]
144 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`168 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`169 このファイルはどのように stable カーネルのリリースが行われるかのルー258 - 4.x.y -stable カーネルツリー298 4.x.y -stable カーネルツリー301 バージョン番号が3つの数字に分かれているカーネルは -stable カーネルです。311 4.x.y は "stable" チーム <stable@vger.kernel.org> でメンテされており、317 Documentation/process/stable-kernel-rules.rst ファイルにはどのような種318 類の変更が -stable ツリーに受け入れ可能か、またリリースプロセスがどう
3 :Original: :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`8 Tutto quello che volevate sapere sui rilasci -stable di Linux12 "-stable":41 Procedura per sottomettere patch per i sorgenti -stable49 https://patchwork.kernel.org/bundle/netdev/stable/?state=*51 di revisione -stable, ma dovrebbe seguire le procedure descritte in68 Cc: stable@vger.kernel.org80 stable@vger.kernel.org includendo: il titolo della patch, l'identificativo90 precedenza, a stable@vger.kernel.org. Dovete annotare nel changelog121 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle[all …]
12 stable/14 defined to be stable. Userspace programs are free to use these21 This directory documents interfaces that are felt to be stable,28 be marked stable. Programs that use these interfaces are71 Interfaces in stable may move to obsolete, as long as the proper77 Interfaces in the testing state can move to the stable state when the86 stable:95 itself. See Documentation/process/stable-api-nonsense.rst.
3 * Interfaces to retrieve and set PDC Stable options (firmware)8 * "A minimum of 96 bytes of Stable Storage is required. Providing more than9 * 96 bytes of Stable Storage is optional [...]. Failure to provide the15 * following code can deal with just 96 bytes of Stable Storage, and all62 #define PDCS_PREFIX "PDC Stable Storage"75 MODULE_DESCRIPTION("sysfs interface to HP PDC Stable Storage data");79 /* holds Stable Storage size. Initialized once and for all, no lock needed */89 unsigned long addr; /* entry address in stable storage */130 * The general idea is that you don't read from the Stable Storage every time132 * content of the stable storage WRT various paths in these structs. We read[all …]
64 * Therefore KSM uses two data structures - the stable and the unstable tree.66 * The stable tree holds pointers to all the merged pages (ksm pages), sorted69 * and therefore this tree is called the stable tree.71 * The stable tree node includes information required for reverse75 * KSM maintains two types of nodes in the stable tree:86 * In addition to the stable tree, KSM uses a second data structure called the104 * 4) KSM never flushes the stable tree, which means that even if it were to106 * it is secured in the stable tree. (When we scan a new page, we first107 * compare it against the stable tree, and then against the unstable tree.)110 * stable trees and multiple unstable trees: one of each for each NUMA node.[all …]
4 Yocto Project Releases and the Stable Release Process45 Realize that there can be patches merged onto the stable release70 Stable Release Process73 Once released, the release enters the stable release process at which74 time a person is assigned as the maintainer for that stable release.79 stable release.85 not backported to a stable release. This policy means generic recipe90 Stable release branches have strong maintenance for about a year after97 information about stable branch maintenance at
24 KSM maintains reverse mapping information for KSM pages in the stable28 the node of the stable tree that represents such KSM page points to a30 KSM page points to the stable tree node.33 the stable tree. The tree node becomes a "chain" that links one or42 This way the stable tree lookup computational complexity is unaffected45 stable tree itself.
1 # From https://sourceforge.net/projects/ijbswa/files/Sources/3.0.32%20%28stable%29/2 md5 3a0a8ebdf80e0a29154683e74cbf510b privoxy-3.0.32-stable-src.tar.gz3 sha1 3a298ab2599fc92555c86dc29a37742d7396a0d3 privoxy-3.0.32-stable-src.tar.gz5 sha256 c61de4008c62445ec18f1f270407cbf2372eaba93beaccdc9e3238bb2defeed7 privoxy-3.0.32-stable-src…
70 * @tparam __stable Sort stable.94 * @tparam __stable Sort stable.115 * @tparam __stable Sort stable.135 * @tparam __stable Sort stable.156 * @tparam __stable Sort stable.178 * @tparam __stable Sort stable.198 * @tparam __stable Sort stable.
15 Some encoders have both outputs low in stable states, others also have16 a stable state with both outputs high (half-period mode) and some have17 a stable state in all steps (quarter-period mode).50 rotational direction based on the last stable state. Events are reported in51 states b) and d) given that the new stable state is different from the last
1 ABI stable symbols4 Documents the interfaces that the developer has defined to be stable.13 .. kernel-abi:: $srctree/Documentation/ABI/stable
7 patches for stable kernels.354 Stable submission357 Q: I need a specific BPF commit in stable kernels. What should I do?359 A: In case you need a specific fix in stable kernels, first check whether362 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/372 Q: Do you also backport to kernels not currently maintained as stable?375 maintained by the stable maintainers, then you are on your own.377 The current stable and longterm stable kernels are all listed here:381 Q: The BPF patch I am about to submit needs to go to stable as well388 Never add "``Cc: stable@vger.kernel.org``" to the patch description, but[all …]
10 SRC_URI = "${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}-stable/${PV}/${BP}.tar.gz \14 UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/"15 UPSTREAM_CHECK_REGEX = "log4cplus-stable/(?P<pver>\d+(\.\d+)+)/"
210 * smp_processor_id() - get the current (stable) CPU id215 * The CPU id is stable when:222 * when smp_processor_id() is used when the CPU id is not stable.226 * Allow the architecture to differentiate between a stable and unstable read.228 * regular asm read for the stable.