Home
last modified time | relevance | path

Searched refs:changes (Results 1 – 25 of 717) sorted by relevance

12345678910>>...29

/linux/drivers/net/slip/
A Dslhc.c234 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/
A Drefcount-vs-atomic.rst79 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/
A Dchangesets.rst7 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/drivers/net/ethernet/intel/ixgbe/
A Dixgbe_dcb_nl.c32 int changes = 0; in ixgbe_copy_dcb_cfg() local
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()
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()
97 changes |= BIT_PG_TX; in ixgbe_copy_dcb_cfg()
109 changes |= BIT_PFC; in ixgbe_copy_dcb_cfg()
115 changes |= BIT_PFC; in ixgbe_copy_dcb_cfg()
[all …]
/linux/tools/laptop/dslm/
A Ddslm.c78 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/
A Dsysfs-platform_profile28 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
A Dsysfs-class-firmware-attributes227 pending BIOS attribute changes. Also, an uevent_KOBJ_CHANGE is
228 generated when it changes to 1.
233 attribute changes applied
245 Drivers may emit a CHANGE uevent when this value changes and userspace
273 Note that any changes to this attribute requires a reboot
274 for changes to take effect.
285 Note that any changes to this attribute requires a reboot for changes to take effect.
A Dsysfs-driver-aspeed-uart-routing17 Users: OpenBMC. Proposed changes should be mailed to
26 Users: OpenBMC. Proposed changes should be mailed to
/linux/Documentation/translations/zh_TW/admin-guide/
A DREADME.rst58 :ref:`Documentation/process/changes.rst <changes>` 文件，它包含了升級內核
110 :ref:`Documentation/process/changes.rst <changes>`
230 有關更多信息，請參閱 :ref:`Documentation/process/changes.rst <changes>` 。
/linux/Documentation/translations/zh_CN/admin-guide/
A DREADME.rst55 :ref:`Documentation/process/changes.rst <changes>` 文件，它包含了升级内核
107 :ref:`Documentation/process/changes.rst <changes>`
227 有关更多信息，请参阅 :ref:`Documentation/process/changes.rst <changes>` 。
/linux/Documentation/process/
A D7.AdvancedTopics.rst41 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 …]
A D5.Posting.rst78 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/Documentation/userspace-api/media/v4l/
A Dvidioc-dqevent.rst147 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 …]
A Dv4l2.rst84 - Introduce HSV formats and other minor changes.
178 V4L2_EVENT_CTRL_CH_RANGE control event changes flag.
227 latest changes. Added the :ref:`multi-planar API <planar-apis>`.
242 Now, revisions will match the kernel version where the V4L2 API changes
338 the history chapter for API changes.
391 v4l2_buffer changes, added video capture example, various corrections.
402 latest API changes. Closed gaps in the history chapter.
/linux/Documentation/ABI/stable/
A Dsysfs-driver-aspeed-vuart6 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/Documentation/core-api/irq/
A Dirqflags-tracing.rst21 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/drivers/net/wireless/ath/ath5k/
A Dmac80211-ops.c253 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/Documentation/virt/kvm/
A Dreview-checklist.rst23 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/arch/arm/nwfpe/
A DChangeLog20 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/fs/affs/
A DChanges39 - 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/Documentation/admin-guide/
A Dabi-testing.rst12 be aware of changes that can occur before these interfaces move to
17 developers can easily notify them if any changes occur.
/linux/Documentation/maintainer/
A Dmodifying-patches.rst14 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,
/linux/Documentation/filesystems/
A Dxfs-delayed-logging-design.rst12 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
119 actually relatively easy to do - all the changes to logged items are already
125 One of the key changes that delayed logging makes to the operation of the
[all …]
/linux/net/bluetooth/rfcomm/
A Dtty.c865 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/Documentation/bpf/
A Dbpf_devel_QA.rst53 In case your patch has changes in various different subsystems (e.g.
56 the changes and provide their Acked-by's to the patches.
83 Q: How do the changes make their way into Linux?
189 complexity of changes and current patch load.
217 Q: Verifier changes and test cases
225 needed, then we might ask for them before accepting any changes.
230 absolutely crucial to make sure future changes do not accidentally
271 to make those changes available to a wider user base of major
323 describing the use-case for the changes is a must.
340 If you are unable to implement or test the required JIT changes for
[all …]

Completed in 24 milliseconds

12345678910>>...29