/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Vim | 11 …changes to Vim yourself, you must clearly describe in the distribution how to contact you. When th… 13 …dified, as mentioned at I). If you make additional changes the text under a) applies to those chan… 15 …changes, including source code, with every copy of the modified Vim you distribute. This may be do… 17 …a modified Vim which includes changes as mentioned under c), you can distribute it without the sou… 18 …e changes permits you to distribute the changes to the Vim maintainer without fee or restriction, … 19 …changes for at least three years after last distributing the corresponding modified Vim. When the … 22 …e) When the GNU General Public License (GPL) applies to the changes, you can distribute the modifi… 24 …essage is only required for as far as this does not conflict with the license used for the changes. 28 …changes and make them available to the maintainer, including the source code. The preferred way to…
|
/openbmc/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() 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 …]
|
/openbmc/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: 137 Memory ordering guarantees changes: [all …]
|
/openbmc/u-boot/tools/patman/ |
H A D | series.py | 38 self.changes = {} 159 for change in sorted(self.changes, reverse=True): 161 for this_commit, text in self.changes[change]: 178 if self.changes: 189 changes_copy = dict(self.changes) 191 if self.changes.get(version): 200 elif self.changes: 268 if not self.changes.get(version): 269 self.changes[version] = [] 270 self.changes[version].append([commit, info])
|
H A D | commit.py | 29 self.changes = {} 41 if not self.changes.get(version): 42 self.changes[version] = [] 43 self.changes[version].append(info)
|
/openbmc/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
|
/openbmc/openbmc/poky/meta/lib/oe/ |
H A D | buildhistory_analysis.py | 450 changes = [] 516 changes.append(chg) 517 return changes 547 changes = collections.OrderedDict() 569 entry = changes.get(m.hexdigest(), (line, [])) 571 changes[m.hexdigest()] = (line, entry[1] + [desc]) 589 for key, item in changes.items(): 622 changes = [] 627 changes.append(compare_siglists(d.a_blob, d.b_blob, taskdiff=sigsdiff)) 628 return changes [all …]
|
/openbmc/linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
H A 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 …]
|
H A D | link.c | 94 u32 changes, bool active) in iwl_mvm_link_changed() argument 108 if (changes & LINK_CONTEXT_MODIFY_ACTIVE) { in iwl_mvm_link_changed() 171 changes &= ~LINK_CONTEXT_MODIFY_HE_PARAMS; in iwl_mvm_link_changed() 192 if (changes & LINK_CONTEXT_MODIFY_EHT_PARAMS) { in iwl_mvm_link_changed() 195 changes &= ~LINK_CONTEXT_MODIFY_EHT_PARAMS; in iwl_mvm_link_changed() 223 cmd.modify_mask = cpu_to_le32(changes); in iwl_mvm_link_changed() 230 if (!ret && (changes & LINK_CONTEXT_MODIFY_ACTIVE)) in iwl_mvm_link_changed()
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | release-notes-5.2.rst | 21 - Kernel-related changes: 78 - Architecture-specific changes: 82 - QEMU / ``runqemu`` changes: 84 - Documentation changes: 92 - Go changes: 103 - Rust changes: 108 - Wic Image Creator changes: 115 - SDK-related changes: 125 - Testing-related changes: 139 - Lots of changes and improvements to the :term:`Toaster` OEQA tests. [all …]
|
H A D | migration-4.3.rst | 41 .. _migration-4.3-compiling-changes: 43 Compiling changes 82 .. _migration-4.3-go-changes: 84 Go language changes 90 .. _migration-4.3-systemd-changes: 92 systemd changes 99 .. _migration-4.3-recipe-changes: 101 Recipe changes 141 - ``glide``: as explained in :ref:`migration-4.3-go-changes`. 155 - ``glide``: as explained in :ref:`migration-4.3-go-changes`. [all …]
|
H A D | migration-5.1.rst | 12 .. _migration-5.1-workdir-changes: 14 :term:`WORKDIR` changes 53 without changes. We cannot use symlinks to do this as it breaks autotools 55 as it meant more invasive recipes changes. The key objective was separating the 58 Previously, :term:`S` was always created but after the recent changes it is no 102 .. _migration-5.1-go-changes: 104 Go language changes 116 .. _migration-5.1-systemd-changes: 118 systemd changes 125 .. _migration-5.1-recipe-changes: [all …]
|
H A D | migration-5.0.rst | 50 .. _migration-5.0-go-changes: 52 Go language changes 59 .. _migration-5.0-systemd-changes: 61 systemd changes 70 .. _migration-5.0-recipe-changes: 72 Recipe changes 122 .. _migration-5.0-qemu-changes: 124 QEMU changes 132 ipk packaging changes 167 .. _migration-5.0-misc-changes: [all …]
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | configuration.md | 5 Configuration changes that should be applied to a device or regulator rail. 6 These changes usually override hardware default settings. 12 The configuration changes are applied during the boot before regulators are 15 The configuration changes are applied by executing one or more actions. The 26 …gs | One or more comment lines describing the configuration changes. …
|
/openbmc/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 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 …]
|
/openbmc/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
|
/openbmc/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()
|
/openbmc/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>` 。
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | quilt.rst | 7 that allows you to capture source code changes without having a clean 9 modify source code, test changes, and then preserve the changes in the 14 With regard to preserving changes to source files, if you clean a 45 #. *Edit the Files:* Make your changes in the source code to the files 49 easiest way to test your changes is by calling the :ref:`ref-tasks-compile` 68 #. *Generate the Patch:* Once your changes work as expected, you need to
|
/openbmc/linux/drivers/net/ethernet/intel/ixgbe/ |
H A 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 …]
|
/openbmc/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>` 230 有關更多信息,請參閱 :ref:`Documentation/process/changes.rst <changes>` 。
|
/openbmc/docs/development/ |
H A D | gerrit-setup.md | 97 changes and push them to Gerrit for code review. Here is what the basic workflow 100 - Make your code changes 103 - Commit your changes, adding a Signed-off-by line to it (more on 104 … commit messages](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes)): 106 - Push your changes to Gerrit for code review: 114 set up Gerrit and know how to submit your code changes for review! 116 Submitting changes for review is just one of many steps in the contributing
|
/openbmc/openbmc/meta-raspberrypi/docs/ |
H A D | Makefile | 184 .PHONY: changes 185 changes: target 186 $(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
|
/openbmc/openbmc/poky/documentation/overview-manual/ |
H A D | development-environment.rst | 153 is usually named "poky", allows you to make changes, contribute to the 235 responsible for accepting changes from other developers and for 250 area. These branches hold changes (commits) to the project that have 253 determines if the changes are qualified to be moved from the "contrib" 259 develop changes. When a developer is satisfied with a particular feature 270 There is a somewhat formal method by which developers commit changes and 274 submitting patches and changes, see the 275 ":doc:`../contributor-guide/submit-changes`" section in the Yocto Project 278 In summary, there is a single point of entry for changes into the 281 develop, test, and submit changes to "contrib" areas for the maintainer [all …]
|
/openbmc/openbmc/poky/documentation/contributor-guide/ |
H A D | submit-changes.rst | 89 for your changes, starting from the reference branch in the upstream 93 $ git checkout -b my-changes 95 If you have completely unrelated sets of changes to submit, you should even 98 Implement and commit changes 101 In each branch, you should group your changes into small, controlled and 102 isolated ones. Keeping changes small and isolated aids review, makes 108 …e <https://www.kernel.org/doc/html/latest/process/submitting-patches.html#separate-your-changes>`__ 116 #. *Stage Your Changes:* Stage your changes by using the ``git add`` 168 changes. Thus, providing something short and descriptive that 218 tested your changes or reviewed their code. These fields are [all …]
|