| /Linux-v6.6/drivers/net/slip/ |
| D | slhc.c | 234 short changes = 0; in slhc_compress() local
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()
419 changes = SPECIAL_I; in slhc_compress()
426 changes = SPECIAL_D; in slhc_compress()
434 changes |= NEW_I; in slhc_compress()
437 changes |= TCP_PUSH_BIT; in slhc_compress()
[all …]
|
| /Linux-v6.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 …]
|
| /Linux-v6.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
|
| /Linux-v6.6/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | mld-mac80211.c | 630 u64 changes) in iwl_mvm_mld_link_info_changed_station() argument
644 if (changes & BSS_CHANGED_QOS && vif->cfg.assoc && link_conf->qos) in iwl_mvm_mld_link_info_changed_station()
647 if (changes & BSS_CHANGED_ERP_SLOT) in iwl_mvm_mld_link_info_changed_station()
656 if (changes & BSS_CHANGED_EHT_PUNCTURING && vif->cfg.assoc && has_eht) in iwl_mvm_mld_link_info_changed_station()
673 iwl_mvm_bss_info_changed_station_common(mvm, vif, link_conf, changes); in iwl_mvm_mld_link_info_changed_station()
714 u64 changes) in iwl_mvm_mld_vif_cfg_changed_station() argument
725 if (changes == BSS_CHANGED_IDLE) in iwl_mvm_mld_vif_cfg_changed_station()
734 if (changes & BSS_CHANGED_ASSOC) { in iwl_mvm_mld_vif_cfg_changed_station()
798 iwl_mvm_bss_info_changed_station_assoc(mvm, vif, changes); in iwl_mvm_mld_vif_cfg_changed_station()
801 if (changes & BSS_CHANGED_PS) { in iwl_mvm_mld_vif_cfg_changed_station()
[all …]
|
| D | link.c | 99 u32 changes, bool active) in iwl_mvm_link_changed() argument
113 if (changes & LINK_CONTEXT_MODIFY_ACTIVE) { in iwl_mvm_link_changed()
176 changes &= ~LINK_CONTEXT_MODIFY_HE_PARAMS; in iwl_mvm_link_changed()
201 changes &= ~LINK_CONTEXT_MODIFY_EHT_PARAMS; in iwl_mvm_link_changed()
225 cmd.modify_mask = cpu_to_le32(changes); in iwl_mvm_link_changed()
232 if (!ret && (changes & LINK_CONTEXT_MODIFY_ACTIVE)) in iwl_mvm_link_changed()
|
| /Linux-v6.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
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
132 should not be making changes to the core memory management code. And, most
[all …]
|
| /Linux-v6.6/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.
102 Setting this value also immediately changes the LED state.
115 Setting this value also immediately changes the LED state.
128 Setting this value also immediately changes the LED state.
141 Setting this value also immediately changes the LED state.
|
| /Linux-v6.6/tools/laptop/dslm/ |
| D | dslm.c | 78 int changes = 0; in measure() local
92 changes++; in measure()
107 changes--; /* Compensate for SIGINT */ in measure()
111 printf(" State changed %d times\n", changes); in measure()
|
| /Linux-v6.6/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>` 。
|
| /Linux-v6.6/drivers/net/ethernet/intel/ixgbe/ |
| D | ixgbe_dcb_nl.c | 30 int changes = 0; in ixgbe_copy_dcb_cfg() local
39 changes |= BIT_APP_UPCHG; in ixgbe_copy_dcb_cfg()
48 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
53 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
58 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
65 changes |= (BIT_PG_TX | BIT_PFC | BIT_APP_UPCHG); in ixgbe_copy_dcb_cfg()
70 changes |= BIT_PG_RX; in ixgbe_copy_dcb_cfg()
75 changes |= BIT_PG_RX; in ixgbe_copy_dcb_cfg()
80 changes |= BIT_PG_RX; in ixgbe_copy_dcb_cfg()
87 changes |= (BIT_PG_RX | BIT_PFC | BIT_APP_UPCHG); in ixgbe_copy_dcb_cfg()
[all …]
|
| /Linux-v6.6/Documentation/translations/zh_TW/admin-guide/ |
| D | README.rst | 58 :ref:`Documentation/process/changes.rst <changes>` 文件，它包含了升級內核
110 :ref:`Documentation/process/changes.rst <changes>`
230 有關更多信息，請參閱 :ref:`Documentation/process/changes.rst <changes>` 。
|
| /Linux-v6.6/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
|
| /Linux-v6.6/drivers/input/joystick/ |
| D | sensehat-joystick.c | 37 unsigned long curr_states, changes; in sensehat_joystick_report() local
49 bitmap_xor(&changes, &curr_states, &sensehat_joystick->prev_states, in sensehat_joystick_report()
52 for_each_set_bit(i, &changes, ARRAY_SIZE(keymap)) in sensehat_joystick_report()
|
| /Linux-v6.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 …]
|
| /Linux-v6.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
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
|
| /Linux-v6.6/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
|
| /Linux-v6.6/Documentation/mm/damon/ |
| D | maintainer-profile.rst | 30 When making DAMON changes, you should do below.
32 - Build changes related outputs including kernel and documents.
38 - Run damon-tests/corr [6]_ for normal changes.
39 - Run damon-tests/perf [7]_ for performance changes.
|
| /Linux-v6.6/Documentation/virt/kvm/ |
| D | review-checklist.rst | 23 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
27 are better than duplicating changes to vendor code.
29 9. Similarly, prefer changes to arch independent code than to arch dependent
|
| /Linux-v6.6/drivers/pinctrl/starfive/ |
| D | Kconfig | 18 and interrupts on input changes.
39 and interrupts on input changes.
51 and interrupts on input changes.
|
| /Linux-v6.6/drivers/net/wireless/ath/ath5k/ |
| D | mac80211-ops.c | 253 struct ieee80211_bss_conf *bss_conf, u64 changes) in ath5k_bss_info_changed() argument
261 if (changes & BSS_CHANGED_BSSID) { in ath5k_bss_info_changed()
268 if (changes & BSS_CHANGED_BEACON_INT) in ath5k_bss_info_changed()
271 if (changes & BSS_CHANGED_ERP_SLOT) { in ath5k_bss_info_changed()
280 if (changes & BSS_CHANGED_ASSOC) { in ath5k_bss_info_changed()
301 if (changes & BSS_CHANGED_BEACON) { in ath5k_bss_info_changed()
307 if (changes & BSS_CHANGED_BEACON_ENABLED) in ath5k_bss_info_changed()
310 if (changes & (BSS_CHANGED_BEACON | BSS_CHANGED_BEACON_ENABLED | in ath5k_bss_info_changed()
|
| /Linux-v6.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.
53 * user_fp and FPA11 have now been harmonized. Most of the changes
88 * ChangeLog - Added this file to track changes made.
|
| /Linux-v6.6/Documentation/gpu/ |
| D | automated_testing.rst | 10 Making sure that changes to the core or drivers don't introduce regressions can
99 If your changes to the code fix any tests, you will have to remove one or more
108 If your code changes make it possible to run more tests (by solving reliability
117 How to test your changes to the scripts
120 For testing changes to the scripts in the drm-ci repo, change the
129 Often, regressions in other trees will prevent testing changes local to the
|
| /Linux-v6.6/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.
|
