/linux/drivers/net/slip/ |
H A 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() 434 changes |= NEW_I; in slhc_compress() 460 *cp++ = changes; in slhc_compress() 495 int changes; in slhc_uncompress() local 509 changes = *cp++; in slhc_uncompress() [all …]
|
/linux/Documentation/core-api/ |
H A 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: 145 Function changes: [all …]
|
/linux/Documentation/devicetree/ |
H A 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/Documentation/process/ |
H A 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 153 If changes do not fit into the normal patterns, there can be additional 165 changes or address problems identified while testing the first set. [all …]
|
H A 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 144 your tree is, what branch to pull, and what changes will result from the [all …]
|
/linux/tools/laptop/dslm/ |
H A 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/Documentation/ABI/testing/ |
H A 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
|
H A 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.
|
/linux/Documentation/dev-tools/ |
H A D | checkuapi.rst | 25 dirty changes, HEAD will be used. 78 Checking changes to UAPI headers between HEAD and dirty tree... 102 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... 190 Checking changes to UAPI headers between HEAD~2 and HEAD... 194 2 data member changes: 249 2 data member changes (1 filtered): 291 2 data member changes: 351 Checking changes to UAPI headers between v6.0 and v6.1... [all …]
|
/linux/Documentation/translations/zh_CN/admin-guide/ |
H A 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/Documentation/translations/zh_TW/admin-guide/ |
H A D | README.rst | 58 :ref:`Documentation/process/changes.rst <changes>` 文件,它包含了升級內核 110 :ref:`Documentation/process/changes.rst <changes>` 231 有關更多信息,請參閱 :ref:`Documentation/process/changes.rst <changes>` 。
|
/linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
H A D | mld-mac80211.c | 768 u64 changes) in iwl_mvm_mld_link_info_changed_station() argument 785 if (changes & BSS_CHANGED_ERP_SLOT) in iwl_mvm_mld_link_info_changed_station() 860 u64 changes) in iwl_mvm_mld_vif_cfg_changed_station() argument 871 if (changes == BSS_CHANGED_IDLE) in iwl_mvm_mld_vif_cfg_changed_station() 880 if (changes & BSS_CHANGED_ASSOC) { in iwl_mvm_mld_vif_cfg_changed_station() 955 if (changes & BSS_CHANGED_PS) { in iwl_mvm_mld_vif_cfg_changed_station() 971 u64 changes) in iwl_mvm_mld_link_info_changed_ap_ibss() argument 1013 u64 changes) in iwl_mvm_mld_link_info_changed() argument 1022 changes); in iwl_mvm_mld_link_info_changed() 1027 changes); in iwl_mvm_mld_link_info_changed() [all …]
|
/linux/drivers/net/ethernet/intel/ixgbe/ |
H A D | ixgbe_dcb_nl.c | 30 int changes = 0; in ixgbe_copy_dcb_cfg() local 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() 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() 95 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg() 107 changes |= BIT_PFC; in ixgbe_copy_dcb_cfg() 113 changes |= BIT_PFC; in ixgbe_copy_dcb_cfg() [all …]
|
/linux/Documentation/ABI/stable/ |
H A 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/drivers/input/joystick/ |
H A 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/Documentation/userspace-api/media/v4l/ |
H A D | vidioc-dqevent.rst | 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`. 314 .. _ctrl-changes-flags: [all …]
|
/linux/Documentation/filesystems/xfs/ |
H A 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/Documentation/core-api/irq/ |
H A 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/Documentation/virt/kvm/ |
H A 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/drivers/pinctrl/starfive/ |
H A D | Kconfig | 18 and interrupts on input changes. 39 and interrupts on input changes. 51 and interrupts on input changes.
|
/linux/tools/include/uapi/ |
H A D | README | 37 process, points out changes in the original files. 39 So its important not to touch the copies in tools/ when doing changes in 52 notification mechanism to look at new kernel side changes. 68 notification to tooling maintainers that there's changes on the kernel
|
/linux/drivers/net/wireless/ath/ath5k/ |
H A 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/Documentation/userspace-api/gpio/ |
H A 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 52 Once a watch is set, any changes to line info will generate events which can be
|
H A 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 57 Once a watch is set, any changes to line info will generate events which can be
|
/linux/arch/arm/nwfpe/ |
H A 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.
|