| /Linux-v5.4/drivers/net/slip/ |
| D | slhc.c | 234 short changes = 0; in slhc_compress() local
366 changes |= NEW_U; in slhc_compress()
376 changes |= NEW_W; in slhc_compress()
382 changes |= NEW_A; in slhc_compress()
388 changes |= NEW_S; in slhc_compress()
391 switch(changes){ in slhc_compress()
413 changes = SPECIAL_I; in slhc_compress()
420 changes = SPECIAL_D; in slhc_compress()
428 changes |= NEW_I; in slhc_compress()
431 changes |= TCP_PUSH_BIT; in slhc_compress()
[all …]
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/ |
| D | changesets.txt | 1 A DT changeset is a method which allows one to apply changes
2 in the live tree in such a way that either the full set of changes
8 When a changeset is applied, all of the changes get applied to the tree
20 a set of changes. No changes to the active tree are made at this point.
24 3. of_changeset_apply() - Apply the changes to the tree. Either the
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-backlight | 9 hence linear changes in brightness are perceived as being
10 non-linear. To achieve a linear perception of brightness changes
20 The brightness changes linearly with each step. Brightness
25 The brightness changes non-linearly with each step. Brightness
|
| /Linux-v5.4/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-v5.4/drivers/net/ethernet/intel/ixgbe/ |
| D | ixgbe_dcb_nl.c | 32 int changes = 0; in ixgbe_copy_dcb_cfg() local
41 changes |= BIT_APP_UPCHG; in ixgbe_copy_dcb_cfg()
50 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
55 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
60 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
67 changes |= (BIT_PG_TX | BIT_PFC | BIT_APP_UPCHG); in ixgbe_copy_dcb_cfg()
72 changes |= BIT_PG_RX; in ixgbe_copy_dcb_cfg()
77 changes |= BIT_PG_RX; in ixgbe_copy_dcb_cfg()
82 changes |= BIT_PG_RX; in ixgbe_copy_dcb_cfg()
89 changes |= (BIT_PG_RX | BIT_PFC | BIT_APP_UPCHG); in ixgbe_copy_dcb_cfg()
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | lt3651-charger.txt | 17 The driver will attempt to aquire interrupts for all GPIOs to detect changes in
19 cannot report changes and userspace will need to periodically read the sysfs
20 attributes to detect changes.
|
| /Linux-v5.4/Documentation/process/ |
| 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 …]
|
| D | index.rst | 14 it much easier for you to get your changes merged with a minimum of
40 changes
|
| 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 …]
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-dqevent.rst | 152 control's value changes, if a button control is pressed or if the
170 second-oldest event is kept, but the ``changes`` field of the
171 second-oldest event is ORed with the ``changes`` field of the
198 associated with it. The ``changes`` bitfield denotes what has
200 application could dequeue them, then the changes will have the
205 the regions changes. This event has a struct
239 - ``changes``
242 :ref:`ctrl-changes-flags`.
314 - ``changes``
316 :ref:`src-changes-flags`.
[all …]
|
| D | v4l2.rst | 89 - Introduce HSV formats and other minor changes.
183 V4L2_EVENT_CTRL_CH_RANGE control event changes flag.
232 latest changes. Added the :ref:`multi-planar API <planar-apis>`.
247 Now, revisions will match the kernel version where the V4L2 API changes
343 the history chapter for API changes.
396 v4l2_buffer changes, added video capture example, various corrections.
407 latest API changes. Closed gaps in the history chapter.
|
| /Linux-v5.4/Documentation/ |
| D | irqflags-tracing.txt | 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-v5.4/Documentation/virt/kvm/ |
| D | review-checklist.txt | 20 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
24 are better than duplicating changes to vendor code.
26 9. Similarly, prefer changes to arch independent code than to arch dependent
|
| /Linux-v5.4/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
|
| /Linux-v5.4/drivers/net/wireless/ath/ath5k/ |
| D | mac80211-ops.c | 253 struct ieee80211_bss_conf *bss_conf, u32 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-v5.4/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-v5.4/mm/ |
| D | vmstat.c | 687 int changes = 0; in fold_diff() local
692 changes++; in fold_diff()
698 changes++; in fold_diff()
704 changes++; in fold_diff()
706 return changes; in fold_diff()
712 int changes = 0; in fold_diff() local
717 changes++; in fold_diff()
723 changes++; in fold_diff()
725 return changes; in fold_diff()
755 int changes = 0; in refresh_cpu_vm_stats() local
[all …]
|
| /Linux-v5.4/fs/affs/ |
| D | Changes | 39 - sizeof changes from Kernel Janitor Project
87 - s_lock changes
161 - File mode changes were not updated on disk.
186 - dentry changes. (Thanks to Jes Sorensen for his help.)
204 directory changes).
255 - rename() will not ignore changes in filename
306 - Minor changes to adhere to the new VFS interface.
321 - Several other changes I just cannot remember
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | design.rst | 20 The API should make no changes to the hardware state unless it has
21 specific knowledge that these changes are safe to perform on this
|
| /Linux-v5.4/Documentation/leds/ |
| D | uleds.rst | 28 changes. The device node can also be polled to notify when the brightness value
29 changes.
|
| /Linux-v5.4/drivers/media/v4l2-core/ |
| D | v4l2-event.c | 322 u32 old_changes = old->u.src_change.changes; in v4l2_event_src_replace()
325 old->u.src_change.changes |= old_changes; in v4l2_event_src_replace()
331 new->u.src_change.changes |= old->u.src_change.changes; in v4l2_event_src_merge()
|
| /Linux-v5.4/drivers/net/wireless/ralink/rt2x00/ |
| D | rt2x00mac.c | 557 u32 changes) in rt2x00mac_bss_info_changed() argument
572 if (changes & BSS_CHANGED_BSSID) in rt2x00mac_bss_info_changed()
579 if (changes & BSS_CHANGED_BEACON_ENABLED) { in rt2x00mac_bss_info_changed()
625 if (changes & BSS_CHANGED_ASSOC) { in rt2x00mac_bss_info_changed()
640 if (changes & (BSS_CHANGED_ERP_CTS_PROT | BSS_CHANGED_ERP_PREAMBLE | in rt2x00mac_bss_info_changed()
643 rt2x00lib_config_erp(rt2x00dev, intf, bss_conf, changes); in rt2x00mac_bss_info_changed()
|
| /Linux-v5.4/net/bluetooth/rfcomm/ |
| D | tty.c | 865 u16 changes = 0; in rfcomm_tty_set_termios() local
881 changes |= RFCOMM_RPN_PM_PARITY; in rfcomm_tty_set_termios()
903 changes |= RFCOMM_RPN_PM_XON; in rfcomm_tty_set_termios()
912 changes |= RFCOMM_RPN_PM_XOFF; in rfcomm_tty_set_termios()
920 changes |= RFCOMM_RPN_PM_STOP; in rfcomm_tty_set_termios()
932 changes |= RFCOMM_RPN_PM_DATA; in rfcomm_tty_set_termios()
954 changes |= RFCOMM_RPN_PM_BITRATE; in rfcomm_tty_set_termios()
991 if (changes) in rfcomm_tty_set_termios()
994 RFCOMM_RPN_FLOW_NONE, x_on, x_off, changes); in rfcomm_tty_set_termios()
|
| /Linux-v5.4/Documentation/driver-api/memory-devices/ |
| D | ti-emif.rst | 34 temperature changes
50 EMIF driver registers notifiers for voltage and frequency changes
|
