Home
last modified time | relevance | path

Searched full:release (Results 1 – 25 of 365) sorted by relevance

12345678910>>...15

/Documentation/scsi/
DChangeLog.megaraid_sas1 Release Date : Thu. Jun 19, 2014 17:00:00 PST 2014 -
15 Release Date : Mon. Mar 10, 2014 17:00:00 PST 2014 -
28 Release Date : Sat. Aug 31, 2013 17:00:00 PST 2013 -
38 Release Date : Wed. May 15, 2013 17:00:00 PST 2013 -
60 Release Date : Sat. Feb 9, 2013 17:00:00 PST 2013 -
69 Release Date : Mon. Oct 1, 2012 17:00:00 PST 2012 -
82 Release Date : Tue. Jun 17, 2012 17:00:00 PST 2012 -
92 Release Date : Mon. Mar 19, 2012 17:00:00 PST 2012 -
100 Release Date : Fri. Jan 6, 2012 17:00:00 PST 2010 -
110 Release Date : Wed. Oct 5, 2011 17:00:00 PST 2010 -
[all …]
Dlpfc.rst4 LPFC Driver Release Notes
10 Starting in the 8.0.17 release, the driver began to be targeted strictly
12 (pre 2.6.10). The 8.0.16 release should be used if the driver is to be
20 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
71 At this time, the driver requires the 2.6.12 (if pre-release, 2.6.12-rc1)
DChangeLog.ips34 4.72.01 - I/O Mapped Memory release ( so "insmod ips" does not Fail )
45 4.70.13 - Don't release HA Lock in ips_next() until SC taken off queue
63 4.20.03 - Rename version to coincide with new release schedules
97 - Change version to 3.60 to coincide with ServeRAID release
100 1.00.00 - Initial Public Release
DChangeLog.megaraid1 Release Date : Thu Nov 16 15:32:35 EST 2006 -
17 Release Date : Fri May 19 09:31:45 EST 2006 - Seokmann Ju <sju@lsil.com>
82 Fix: MegaRAID F/W has fixed the problem and being process of release,
140 Release Date : Mon Apr 11 12:27:22 EST 2006 - Seokmann Ju <sju@lsil.com>
165 Release Date : Fri Nov 11 12:27:22 EST 2005 - Seokmann Ju <sju@lsil.com>
200 Release Date : Mon Mar 07 12:27:22 EST 2005 - Seokmann Ju <sju@lsil.com>
266 Release Date : Thu Feb 03 12:27:22 EST 2005 - Seokmann Ju <sju@lsil.com>
282 Release Date : Thu Jan 27 00:01:03 EST 2005 - Atul Mukker <atulm@lsil.com>
288 Release Date : Thu Jan 21 00:01:03 EST 2005 - Atul Mukker <atulm@lsil.com>
349 Release Date : Thu Dec 9 19:10:23 EST 2004
[all …]
/Documentation/driver-api/soundwire/
Dlocking.rst47 c. Release Message lock
62 +-------------------------------> c. Release Message lock
81 c. Release Message lock.
83 3. Release lock for Bus instance associated with Master 1 ::
101 +-------------------------------> c. Release Message lock
105 | return success/error | 3. Release bus lock
/Documentation/process/
D2.Process.rst16 The kernel developers use a loosely time-based release process, with a new
17 major kernel release happening every two or three months. The recent
18 release history looks like this:
29 Every 5.x release is a major kernel release with new features, internal
30 API changes, and more. A typical release can contain about 13,000
36 merging of patches for each release. At the beginning of each development
50 time, Linus Torvalds will declare that the window is closed and release the
52 for example, the release which happens at the end of the merge window will
53 be called 5.6-rc1. The -rc1 release is the signal that the time to
70 considered to be sufficiently stable and the final release is made.
[all …]
Dsecurity-bugs.rst16 who will help verify the bug report and develop and release a fix.
42 Once a robust fix has been developed, the release process starts. Fixes
45 Although our preference is to release fixes for publicly undisclosed bugs
48 of the release process, with an exceptional extension to 14 calendar days
51 the logistics of QA and large scale rollouts which require release
Dmaintainer-kvm-x86.rst51 Fixes that target the current release, a.k.a. mainline, are typically applied
54 Changes that target the next release are routed through the KVM x86 tree. Pull
62 the next release; see above for fixes that target the current release).
68 especially for the current release and or stable trees, get to jump the queue.
77 current release cycle and have realistic expectations. If you are pinging for
87 Fixes that target the current release, a.k.a. mainline, should be based on
89 automatically warrant inclusion in the current release. There is no singular
91 introduced in the current release should target the current release.
102 history, e.g. the release candidate upon which ``kvm-x86 next`` is based. If
230 an older release.
/Documentation/driver-api/acpi/
Dlinuxized-acpica.rst5 Linuxized ACPICA - Introduction to ACPICA Release Automation
116 ACPICA Release
120 https://github.com/acpica/acpica.git. As a rule, a release is made every
124 Linux, there is a release process to convert the ACPICA git commits into
126 "linuxized ACPICA patches". The release process is carried out on a local
127 copy the ACPICA git repository. Each commit in the monthly release is
129 ACPICA release patchset for the Linux ACPI community. This process is
195 the release process fully automatically.
202 1. Legacy divergences - Before the current ACPICA release process was
208 made directly in the Linux sources obviously hurts the ACPICA release
[all …]
/Documentation/devicetree/bindings/arm/
Dcpus.yaml258 cpu-release-addr:
366 code release a secondary CPU. The value written to the register is
465 cpu-release-addr = <0 0x20000000>;
473 cpu-release-addr = <0 0x20000000>;
481 cpu-release-addr = <0 0x20000000>;
489 cpu-release-addr = <0 0x20000000>;
497 cpu-release-addr = <0 0x20000000>;
505 cpu-release-addr = <0 0x20000000>;
513 cpu-release-addr = <0 0x20000000>;
521 cpu-release-addr = <0 0x20000000>;
[all …]
/Documentation/filesystems/xfs/
Dxfs-maintainer-entry-profile.rst46 They should help prioritize development and review work for each release
66 release managers execute on the testing.
78 - **Release Manager**: This person merges reviewed patchsets into an
81 The release manager is not expected to work on new feature patchsets.
83 the release manager must have the ability to intervene to try to drive a
86 The release manager should identify themselves with an ``M:`` entry in
99 The maintainer for a given LTS release should identify themselves with an
167 Key Release Cycle Dates
169 Bug fixes may be sent at any time, though the release manager may decide to
/Documentation/arch/arm/vfp/
Drelease-notes.rst2 Release notes for Linux Kernel VFP support code
9 This is the first release of the Linux Kernel VFP support code. It
13 This release has been validated against the SoftFloat-2b library by
/Documentation/devicetree/bindings/cpu/
Dcpu-topology.txt281 cpu-release-addr = <0 0x20000000>;
289 cpu-release-addr = <0 0x20000000>;
297 cpu-release-addr = <0 0x20000000>;
305 cpu-release-addr = <0 0x20000000>;
313 cpu-release-addr = <0 0x20000000>;
321 cpu-release-addr = <0 0x20000000>;
329 cpu-release-addr = <0 0x20000000>;
337 cpu-release-addr = <0 0x20000000>;
345 cpu-release-addr = <0 0x20000000>;
353 cpu-release-addr = <0 0x20000000>;
[all …]
/Documentation/arch/riscv/
Dacpi.rst9 "riscv-isa-release-1239329-2023-05-23" (commit 1239329
10 ) <https://github.com/riscv/riscv-isa-manual/releases/tag/riscv-isa-release-1239329-2023-05-23>`_
/Documentation/litmus-tests/atomic/
Dcmpxchg-fail-unordered-2.litmus7 * an acquire release operation. (In contrast, a successful cmpxchg()
8 * does act as both an acquire and a release operation.)
/Documentation/core-api/
Drefcount-vs-atomic.rst49 A RELEASE memory ordering guarantees that all prior loads and
53 must propagate to all other CPUs before the release operation
89 case 2) - non-"Read/Modify/Write" (RMW) ops with release ordering
98 * none (both provide RELEASE ordering)
122 * fully unordered --> RELEASE ordering
164 * fully ordered --> RELEASE ordering + ACQUIRE ordering on success
177 * fully ordered --> RELEASE ordering + control dependency
192 * fully ordered --> RELEASE ordering + control dependency + hold
Dkobject.rst203 need to do a kobject_put() eventually to release that reference.
246 ktypes and release methods
268 This notification is done through a kobject's release() method. Usually
280 release() method, and the kobject must persist (in a consistent state)
283 release() method. Do not try to get rid of this warning by providing an
284 "empty" release function.
291 Note, the name of the kobject is available in the release function, but it
295 Interestingly, the release() method is not stored in the kobject itself;
300 void (*release)(struct kobject *kobj);
313 The release field in struct kobj_type is, of course, a pointer to the
[all …]
/Documentation/devicetree/bindings/input/
De3x0-button.txt13 - "press", "release": For devices such as the NI Ettus Research USRP E3x0
22 interrupt-names = "press", "release";
/Documentation/i2c/
Dgpio-fault-injection.rst24 change its state to either force it low or to release it again. So, by using
34 change its state to either force it low or to release it again. So, by using
39 succeed because SDA is still pinned low until you manually release it again
40 with "echo 1 > sda". A test with an automatic release can be done with the
48 there are I2C client devices which detect a stuck SDA on their side and release
64 recovery. This time, however, it should succeed and the device should release
/Documentation/filesystems/
Dlocks.rst4 File Locking Release Notes
20 release of the 2.1.x kernel series, support for the old emulation has
60 Mandatory locking was prior to this release a general configuration option
/Documentation/devicetree/bindings/soc/renesas/
Drenesas,rzg2l-sysc.yaml34 - description: CA55 Software Standby Mode release request interrupt
35 - description: CM33 Software Standby Mode release request interrupt
/Documentation/translations/ko_KR/
Dmemory-barriers.txt504 ACQUIRE 오퍼레이션은 거의 항상 RELEASE 오퍼레이션과 짝을 지어 사용되어야
508 (6) RELEASE 오퍼레이션.
510 이 타입의 오퍼레이션들도 단방향 투과성 배리어처럼 동작합니다. RELEASE
511 오퍼레이션 앞의 모든 메모리 오퍼레이션들은 RELEASE 오퍼레이션 전에 완료된
513 오퍼레이션들과 smp_store_release() 오퍼레이션도 RELEASE 오퍼레이션의
516 RELEASE 오퍼레이션 뒤의 메모리 오퍼레이션들은 RELEASE 오퍼레이션이
519 ACQUIRE 와 RELEASE 오퍼레이션의 사용은 일반적으로 다른 메모리 배리어의
520 필요성을 없앱니다. 또한, RELEASE+ACQUIRE 조합은 범용 메모리 배리어처럼
521 동작할 것을 보장하지 -않습니다-. 하지만, 어떤 변수에 대한 RELEASE
522 오퍼레이션을 앞서는 메모리 액세스들의 수행 결과는 이 RELEASE 오퍼레이션을
[all …]
/Documentation/devicetree/bindings/sound/
Dcs35l36.txt126 release state.
128 - cirrus,vpbr-rel-rate : Attenuation release step rate. Configures the delay
129 between consecutive volume attenuation release steps when a brownout condition
130 is not longer present and the VP brownout is in an attenuation release state.
/Documentation/locking/
Dhwspinlock.rst92 After verifying the owner of the hwspinlock, release a previously acquired
107 the caller must not sleep, and is advised to release the hwspinlock as
124 release the hwspinlock as soon as possible.
141 release the hwspinlock as soon as possible.
190 caller must not sleep, and is advised to release the hwspinlock as soon as
208 release the hwspinlock as soon as possible.
225 to release the hwspinlock as soon as possible.
356 /* release the lock */
391 /* release the lock */
/Documentation/translations/zh_CN/video4linux/
Dv4l2-framework.txt538 vdev->release = video_device_release;
540 如果将其嵌入到一个大结构体中，则必须自己实现 release()回调。
544 vdev->release = my_vdev_release;
546 release()回调必须被设置，且在最后一个 video_device 用户退出之后
702 你也必须释放它。vdev->release() 回调不会在注册失败之后被调用，
718 节点。所以在注销之后，所有文件操作（当然除了 release ）也应返回错误值。
720 当最后一个视频设备节点的用户退出，则 vdev->release() 回调会被调用，
727 这可以在 release 回调中完成。
787 应该在 open() 中调用 v4l2_fh_init+v4l2_fh_add，并在 release() 中
866 这两个函数可以插入到 v4l2_file_operation 的 open() 和 release()

12345678910>>...15