| /kernel/linux/linux-5.10/arch/arm/nwfpe/ |
| D | ChangeLog | 20 floating point registers. Therefore, any changes to the
29 * The changes are designed to break any patch that goes on top
30 of this code, so that the authors properly review their changes.
36 * fpa11.c - Changes due to FPA11, FPREG structure alterations.
37 * fpa11_cpdo.c - Changes due to FPA11, FPREG structure alterations.
38 * fpa11_cpdt.c - Changes due to FPA11, FPREG structure alterations.
39 * fpa11_cprt.c - Changes due to FPA11, FPREG structure alterations.
40 * single_cpdo.c - Changes due to FPA11, FPREG structure alterations.
41 * double_cpdo.c - Changes due to FPA11, FPREG structure alterations.
42 * extended_cpdo.c - Changes due to FPA11, FPREG structure alterations.
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/nwfpe/ |
| D | ChangeLog | 20 floating point registers. Therefore, any changes to the
29 * The changes are designed to break any patch that goes on top
30 of this code, so that the authors properly review their changes.
36 * fpa11.c - Changes due to FPA11, FPREG structure alterations.
37 * fpa11_cpdo.c - Changes due to FPA11, FPREG structure alterations.
38 * fpa11_cpdt.c - Changes due to FPA11, FPREG structure alterations.
39 * fpa11_cprt.c - Changes due to FPA11, FPREG structure alterations.
40 * single_cpdo.c - Changes due to FPA11, FPREG structure alterations.
41 * double_cpdo.c - Changes due to FPA11, FPREG structure alterations.
42 * extended_cpdo.c - Changes due to FPA11, FPREG structure alterations.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 79 Function changes:
84 Memory ordering guarantee changes:
92 Function changes:
97 Memory ordering guarantee changes:
104 Function changes:
108 Memory ordering guarantee changes:
116 Function changes:
121 Memory ordering guarantees changes:
132 Function changes:
137 Memory ordering guarantees changes:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 79 Function changes:
84 Memory ordering guarantee changes:
92 Function changes:
97 Memory ordering guarantee changes:
104 Function changes:
108 Memory ordering guarantee changes:
116 Function changes:
121 Memory ordering guarantees changes:
132 Function changes:
137 Memory ordering guarantees changes:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | maintainer-soc.rst | 25 The SoC subsystem also serves as an intermediate location for changes to
51 changes. Each architecture has its own maintainers that are responsible for
68 If changes are being made to a devicetree that are incompatible with old
70 appropriate time later. Most importantly, any incompatible changes should be
78 A common problem is synchronizing changes between device drivers and devicetree
80 coordinating how the changes get merged through different maintainer trees.
99 * Defer the devicetree changes to a release after the binding and driver have
103 both the driver change and the devicetree changes
145 submaintainers will do the same. Driver, defconfig and devicetree changes should
153 If changes do not fit into the normal patterns, there can be additional
[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 …]
|
| /kernel/uniproton/src/arch/cpu/armv8/common/hwi/ |
| D | prt_vector.S | 61 .org (VBAR + 0x400) // Synchronous, EL changes and the target EL is using AArc…
64 .org (VBAR + 0x480) // IRQ/vIRQ, EL changes and the target EL is using AArch64
67 .org (VBAR + 0x500) // FIQ/vFIQ, EL changes and the target EL is using AArch64
69 .org (VBAR + 0x580) // SERROR, EL changes and the target EL is using AArch64
71 .org (VBAR + 0x600) // Synchronous, L changes and the target EL is using AArch…
74 .org (VBAR + 0x680) // IRQ/vIRQ, EL changes and the target EL is using AArch32
77 .org (VBAR + 0x700) // FIQ/vFIQ, EL changes and the target EL is using AArch32
79 .org (VBAR + 0x780) // SERROR, EL changes and the target EL is using AArch32
|
| /kernel/linux/linux-5.10/Documentation/devicetree/ |
| D | changesets.rst | 7 A DT 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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| 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 | 5.Posting.rst | 78 resolving conflicts and dealing with API changes.
80 Only the most simple changes should be formatted as a single patch;
81 everything else should be made as a logical series of changes. Splitting
87 changes found in your working revision control system. Instead, the
88 changes you have made need to be considered in their final form, then
90 discrete, self-contained changes, not the path you took to get to those
91 changes.
94 patch. These changes can be small ("add a field to this structure") or
101 changes in the same patch. If a single patch fixes a critical security
182 support other changes coming in later patch, say so. If internal APIs are
[all …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-dqevent.rst | 130 control's value changes, if a button control is pressed or if the
148 second-oldest event is kept, but the ``changes`` field of the
149 second-oldest event is ORed with the ``changes`` field of the
176 associated with it. The ``changes`` bitfield denotes what has
178 application could dequeue them, then the changes will have the
183 the regions changes. This event has a struct
215 - ``changes``
217 :ref:`ctrl-changes-flags`.
279 - ``changes``
281 :ref:`src-changes-flags`.
[all …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/drivers/net/slip/ |
| D | slhc.c | 234 short changes = 0; in slhc_compress() local
365 * receiver expects changes in the order: urgent, window, in slhc_compress()
372 changes |= NEW_U; in slhc_compress()
382 changes |= NEW_W; in slhc_compress()
388 changes |= NEW_A; in slhc_compress()
394 changes |= NEW_S; in slhc_compress()
397 switch(changes){ in slhc_compress()
411 /* actual changes match one of our special case encodings -- in slhc_compress()
419 changes = SPECIAL_I; in slhc_compress()
426 changes = SPECIAL_D; in slhc_compress()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/slip/ |
| D | slhc.c | 234 short changes = 0; in slhc_compress() local
365 * receiver expects changes in the order: urgent, window, in slhc_compress()
372 changes |= NEW_U; in slhc_compress()
382 changes |= NEW_W; in slhc_compress()
388 changes |= NEW_A; in slhc_compress()
394 changes |= NEW_S; in slhc_compress()
397 switch(changes){ in slhc_compress()
411 /* actual changes match one of our special case encodings -- in slhc_compress()
419 changes = SPECIAL_I; in slhc_compress()
426 changes = SPECIAL_D; in slhc_compress()
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.rst | 12 logged are made up of the changes to in-core structures rather than on-disk
13 structures. Other objects - typically buffers - have their physical changes
26 changes in the new transaction that is written to the log.
28 That is, if we have a sequence of changes A through to F, and the object was
43 the aggregation of all the previous changes currently held only in the log.
65 the log - repeated operations to the same objects write the same changes to
82 Effectively, this gives us the maximum bound of outstanding metadata changes
101 contains all the changes from the previous changes. In other words, we have one
112 infrastructure to keep track of logical changes in memory prior to physically
113 formatting the changes in a transaction to the log buffer. Hence we cannot avoid
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | mld-mac80211.c | 604 u64 changes) in iwl_mvm_mld_link_info_changed_station() argument
618 if (changes & BSS_CHANGED_QOS && vif->cfg.assoc && link_conf->qos) in iwl_mvm_mld_link_info_changed_station()
621 if (changes & BSS_CHANGED_ERP_SLOT) in iwl_mvm_mld_link_info_changed_station()
630 if (changes & BSS_CHANGED_EHT_PUNCTURING && vif->cfg.assoc) in iwl_mvm_mld_link_info_changed_station()
647 iwl_mvm_bss_info_changed_station_common(mvm, vif, link_conf, changes); in iwl_mvm_mld_link_info_changed_station()
688 u64 changes) in iwl_mvm_mld_vif_cfg_changed_station() argument
699 if (changes == BSS_CHANGED_IDLE) in iwl_mvm_mld_vif_cfg_changed_station()
708 if (changes & BSS_CHANGED_ASSOC) { in iwl_mvm_mld_vif_cfg_changed_station()
772 iwl_mvm_bss_info_changed_station_assoc(mvm, vif, changes); in iwl_mvm_mld_vif_cfg_changed_station()
775 if (changes & BSS_CHANGED_PS) { in iwl_mvm_mld_vif_cfg_changed_station()
[all …]
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | xfs_quota.h | 23 * If, for example, the ownership of the inode changes while
57 * The structure kept inside the xfs_trans_t keep track of dquot changes
64 int64_t qt_bcount_delta; /* dquot blk count changes */
65 int64_t qt_delbcnt_delta; /* delayed dquot blk count changes */
69 int64_t qt_rtbcount_delta;/* dquot realtime blk changes */
70 int64_t qt_delrtb_delta; /* delayed RT blk count changes */
74 int64_t qt_icount_delta; /* dquot inode count changes */
|
| /kernel/linux/linux-6.6/fs/xfs/ |
| D | xfs_quota.h | 23 * If, for example, the ownership of the inode changes while
57 * The structure kept inside the xfs_trans_t keep track of dquot changes
64 int64_t qt_bcount_delta; /* dquot blk count changes */
65 int64_t qt_delbcnt_delta; /* delayed dquot blk count changes */
69 int64_t qt_rtbcount_delta;/* dquot realtime blk changes */
70 int64_t qt_delrtb_delta; /* delayed RT blk count changes */
74 int64_t qt_icount_delta; /* dquot inode count changes */
|