Searched full:changes (Results 1 – 25 of 660) sorted by relevance
12345678910>>...27
| /Documentation/devicetree/ |
| D | changesets.rst | 7 A Devicetree changeset is a method which allows one to apply changes
8 in the live tree in such a way that either the full set of changes
14 When a changeset is applied, all of the changes get applied to the tree
26 a set of changes. No changes to the active tree are made at this point.
30 3. of_changeset_apply() - Apply the changes to the tree. Either the
|
| /Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 79 Function changes:
84 Memory ordering guarantee changes:
92 Function changes:
96 Memory ordering guarantee changes:
104 Function changes:
109 Memory ordering guarantee changes:
116 Function changes:
120 Memory ordering guarantee changes:
128 Function changes:
133 Memory ordering guarantees changes:
[all …]
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 23 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
26 8. Changes should be vendor neutral when possible. Changes to common code
27 are better than duplicating changes to vendor code.
29 9. Similarly, prefer changes to arch independent code than to arch dependent
|
| /Documentation/process/ |
| D | maintainer-soc.rst | 25 The SoC subsystem also serves as an intermediate location for changes to
52 changes. Each architecture has its own maintainers that are responsible for
59 (platform-specific maintainers). This includes also changes to per-platform or
100 If changes are being made to a devicetree that are incompatible with old
102 appropriate time later. Most importantly, any incompatible changes should be
110 A common problem is synchronizing changes between device drivers and devicetree
112 coordinating how the changes get merged through different maintainer trees.
131 * Defer the devicetree changes to a release after the binding and driver have
135 both the driver change and the devicetree changes
177 submaintainers will do the same. Driver, defconfig and devicetree changes should
[all …]
|
| D | 7.AdvancedTopics.rst | 41 of the mainline repository, explore the revision history, commit changes to
74 you have been working on it for months. Changes can be transparently
81 Rewriting history will rewrite the changes contained in that history,
90 So, once you push a set of changes to your publicly-available server, those
91 changes should not be rewritten. Git will attempt to enforce this rule if
92 you try to push changes which do not result in a fast-forward merge
93 (i.e. changes which do not share the same history). It is possible to
101 As the mainline (or other tree upon which a set of changes is based)
109 release). If you are nervous about specific changes, you can always
116 slip in ill-advised changes which go into the mainline below the review
[all …]
|
| D | maintainer-kvm-x86.rst | 54 Changes that target the next release are routed through the KVM x86 tree. Pull
100 and/or has more than superficial changes to other architectures' code. Multi-
163 changes, i.e. for arch/x86/kernel/kvm.c. Do not use file names or complete file
198 a short blurb on the actual changes, and then follow up with the context and
251 obvious, the tests need to pass). The only exception is for changes that have
256 For changes that touch KVM's shadow paging code, running with TDP (EPT/NPT)
257 disabled is mandatory. For changes that affect common KVM MMU code, running
258 with TDP disabled is strongly encouraged. For all other changes, if the code
263 a failure is not due to your changes, verify that the *exact same* failure
264 occurs with and without your changes.
[all …]
|
| D | 2.Process.rst | 30 API changes, and more. A typical release can contain about 13,000
31 changesets with changes to several hundred thousand lines of code. 5.x is
33 rolling development model which is continually integrating major changes.
39 community) is merged into the mainline kernel. The bulk of changes for a
40 new development cycle (and all of the major changes) will be merged during
41 this time, at a rate approaching 1,000 changes ("patches," or "changesets")
44 (As an aside, it is worth noting that the changes integrated during the
101 worse; the pile of changes waiting for the next merge window will grow
148 and controversial changes, go on for years. Much developer frustration
181 getting feedback about changes that are needed, you should either
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-maintainer-entry-profile.rst | 118 context of the changes unnecessarily difficult.
120 - Anyone making kernel changes that have corresponding changes to the
121 userspace utilities should send the userspace changes as separate
160 - Changes to the on-disk format of XFS must be described in the ondisk
174 This gives the community time to review the changes, to suggest other changes,
175 and for the author to retest those changes.
177 Code submissions also requiring changes to fs/iomap and targeting the
180 infrastructure changes.
186 developers that have Reviewed-by tags for XFS changes to take a look and
|
| D | xfs-delayed-logging-design.rst | 26 XFS uses Write Ahead Logging for ensuring changes to the filesystem metadata
33 details logged are made up of the changes to in-core structures rather than
35 changes logged. Long running atomic modifications have individual changes
108 this provides a mechanism for complex changes to appear atomic from an external
167 take into account all the hidden changes that might occur.
311 existing changes in the new transaction that is written to the log.
313 That is, if we have a sequence of changes A through to F, and the object was
328 the aggregation of all the previous changes currently held only in the log.
347 the log - repeated operations to the same objects write the same changes to
365 Effectively, this gives us the maximum bound of outstanding metadata changes
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform_profile | 28 platform_profile_choices changes the profile to the new value.
30 This file can be monitored for changes by polling for POLLPRI,
31 POLLPRI will be signalled on any changes, independent of those
32 changes coming from a userspace write; or coming from another
|
| D | sysfs-class-led-trigger-netdev | 32 Setting this value also immediately changes the LED state.
89 Setting this value also immediately changes the LED state.
104 Setting this value also immediately changes the LED state.
119 Setting this value also immediately changes the LED state.
134 Setting this value also immediately changes the LED state.
149 Setting this value also immediately changes the LED state.
164 Setting this value also immediately changes the LED state.
179 Setting this value also immediately changes the LED state.
192 Setting this value also immediately changes the LED state.
|
| /Documentation/driver-api/media/drivers/ |
| D | rkisp1.rst | 9 The rkisp1 block underwent some changes between SoC implementations.
25 has seen really big changes in the vendor kernel, so will need
28 Changes from V10 to V12
38 Changes from V12 to V13
|
| /Documentation/dev-tools/ |
| D | checkuapi.rst | 24 will use any dirty changes in tree to UAPI files. If there are no
25 dirty changes, HEAD will be used.
31 -i Ignore ambiguous changes that may or may not break UAPI compatibility.
78 Checking changes to UAPI headers between HEAD and dirty tree...
102 Checking changes to UAPI headers between HEAD and dirty tree...
120 anything. You can pass the ``-i`` flag to the script to ignore changes
126 Checking changes to UAPI headers between HEAD and dirty tree...
152 Checking changes to UAPI headers between HEAD and dirty tree...
156 2 data member changes:
177 Checking changes to UAPI headers between HEAD^1 and HEAD...
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-aspeed-vuart | 6 Users: OpenBMC. Proposed changes should be mailed to
14 Users: OpenBMC. Proposed changes should be mailed to
23 Users: OpenBMC. Proposed changes should be mailed to
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-dqevent.rst | 129 control's value changes, if a button control is pressed or if the
147 second-oldest event is kept, but the ``changes`` field of the
148 second-oldest event is ORed with the ``changes`` field of the
175 associated with it. The ``changes`` bitfield denotes what has
177 application could dequeue them, then the changes will have the
182 the regions changes. This event has a struct
214 - ``changes``
216 :ref:`ctrl-changes-flags`.
278 - ``changes``
280 :ref:`src-changes-flags`.
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-v2-get-lineinfo-watch-ioctl.rst | 12 GPIO_V2_GET_LINEINFO_WATCH_IOCTL - Enable watching a line for changes to its
35 Enable watching a line for changes to its request state and configuration
36 information. Changes to line info include a line being requested, released
52 Once a watch is set, any changes to line info will generate events which can be
|
| D | gpio-get-lineinfo-watch-ioctl.rst | 16 GPIO_GET_LINEINFO_WATCH_IOCTL - Enable watching a line for changes to its
39 Enable watching a line for changes to its request state and configuration
40 information. Changes to line info include a line being requested, released
57 Once a watch is set, any changes to line info will generate events which can be
|
| /Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 21 state changes. But an architecture can be irq-flags-tracing enabled in a
25 code-organizational changes first:
29 and then a couple of functional changes are needed as well to implement
50 changes break other code by modifying conditions or registers that
|
| /Documentation/admin-guide/cifs/ |
| D | changes.rst | 2 Changes title
6 information about fixes/improvements to CIFS/SMB2/SMB3 support (changes
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 28 --dump-die-map Print debugging information about die_map changes
92 changes to kernel data structures due to LTS updates or backports. Using
93 the traditional `#ifndef __GENKSYMS__` to hide these changes from symbol
96 hide changes that won't affect the ABI when calculating versions. These
105 ensuring that their changes actually won't break the ABI.
121 - `version`: Ensures backward compatibility for future changes to the
149 are pulled into the translation unit. This changes the versions of any
229 Managing structure size changes
272 In rare situations where distributions must make significant changes to
308 going unnoticed as it hides all changes to the type.
[all …]
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 12 be aware of changes that can occur before these interfaces move to
17 developers can easily notify them if any changes occur.
|
| /Documentation/scsi/ |
| D | ChangeLog.lpfc | 5 Changes from 20050323 to 20050413
27 * Changes in lpfc_abort_handler(): Return SUCCESS if we did not
47 Changes from 20050308 to 20050323
79 Changes from 20050223 to 20050308
98 Changes from 20050215 to 20050223
141 Changes from 20050208 to 20050215
169 Changes from 20050201 to 20050208
207 * VPD changes: 1) Modify driver to use the model name and
213 Changes from 20050124 to 20050201
276 Changes from 20050110 to 20050124
[all …]
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | README.rst | 58 :ref:`Documentation/process/changes.rst <changes>` 文件，它包含了升級內核
110 :ref:`Documentation/process/changes.rst <changes>`
231 有關更多信息，請參閱 :ref:`Documentation/process/changes.rst <changes>` 。
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | README.rst | 55 :ref:`Documentation/process/changes.rst <changes>` 文件，它包含了升级内核
107 :ref:`Documentation/process/changes.rst <changes>`
228 有关更多信息，请参阅 :ref:`Documentation/process/changes.rst <changes>` 。
|
| /Documentation/maintainer/ |
| D | modifying-patches.rst | 14 yours, indicating the nature of your changes. While there is nothing mandatory
17 that you are responsible for last-minute changes. Example::
24 want at the same time to credit the author, track changes, merge the fix,
|
12345678910>>...27