| /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…
|
| H A D | PolyForm-Noncommercial-1.0.0 | 18 License](#distribution-license) and make changes or new works
19 based on the software according to [Changes and New Works
20 License](#changes-and-new-works-license).
27 changes and new works permitted by [Changes and New Works
28 License](#changes-and-new-works-license).
40 ## Changes and New Works License
43 make changes and new works based on the software for any
|
| H A D | PolyForm-Small-Business-1.0.0 | 18 License](#distribution-license) and make changes or new works
19 based on the software according to [Changes and New Works
20 License](#changes-and-new-works-license).
27 changes and new works permitted by [Changes and New Works
28 License](#changes-and-new-works-license).
40 ## Changes and New Works License
43 make changes and new works based on the software for any
|
| /openbmc/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.
36 * fpa11.c - Changes due to FPA11, FPREG structure alterations.
37 * fpa11_cpdo.c - Changes due to FPA11, FPREG structure alterations.
38 * fpa11_cpdt.c - Changes due to FPA11, FPREG structure alterations.
39 * fpa11_cprt.c - Changes due to FPA11, FPREG structure alterations.
40 * single_cpdo.c - Changes due to FPA11, FPREG structure alterations.
41 * double_cpdo.c - Changes due to FPA11, FPREG structure alterations.
42 * extended_cpdo.c - Changes due to FPA11, FPREG structure alterations.
[all …]
|
| /openbmc/openbmc/poky/documentation/contributor-guide/ |
| H A D | submit-changes.rst | 3 Contributing Changes to a Component
51 Preparing Changes for Submission
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``
[all …]
|
| /openbmc/u-boot/tools/patman/ |
| H A D | series.py | 16 valid_series = ['to', 'cc', 'version', 'changes', 'prefix', 'notes', 'name',
27 changes: (dict) List of changes for each version, The key is
38 self.changes = {}
140 """Create a list of changes for each version.
145 Changes in v4:
148 Changes in v3: None
149 Changes in v2:
159 for change in sorted(self.changes, reverse=True):
161 for this_commit, text in self.changes[change]:
166 line = 'Changes in v%d:' % change
[all …]
|
| H A D | commit.py | 20 changes: Dict containing a list of changes (single line strings).
29 self.changes = {}
41 if not self.changes.get(version):
42 self.changes[version] = []
43 self.changes[version].append(info)
|
| /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/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/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 …]
|
| H A D | 7.AdvancedTopics.rst | 41 of the mainline repository, explore the revision history, commit changes to
74 you have been working on it for months. Changes can be transparently
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
[all …]
|
| /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-2.6.rst | 9 .. _migration-2.6-gcc-changes:
16 release, see https://gcc.gnu.org/gcc-8/changes.html.
78 .. _migration-2.6-packaging-changes:
80 Packaging Changes
83 The following packaging changes have been made:
152 .. _migration-2.6-image-kernel-artifact-naming-changes:
154 Image/Kernel Artifact Naming Changes
157 The following changes have been made:
162 allows easier and more direct changes.
236 .. _migration-2.6-override-changes:
[all …]
|
| H A D | migration-1.7.rst | 9 .. _migration-1.7-changes-to-setting-qemu-packageconfig-options:
11 Changes to Setting QEMU ``PACKAGECONFIG`` Options in ``local.conf``
39 .. _migration-1.7-autotools-class-changes:
41 Autotools Class Changes
44 The following :ref:`ref-classes-autotools` class changes occurred:
116 replacement should not require any significant changes to other software
117 that links to ``eglibc``. However, there were a number of minor changes
124 For full details on the changes in ``glibc 2.20``, see the upstream
148 .. _migration-1.7-qa-check-changes:
150 QA Check 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-1.6.rst | 19 .. _migration-1.6-packaging-changes:
21 Packaging Changes
24 The following packaging changes have been made:
47 The following changes have been made to :term:`BitBake`.
123 .. _migration-1.6-variable-changes:
125 Changes to Variables
131 .. _migration-1.6-variable-changes-TMPDIR:
143 .. _migration-1.6-variable-changes-PRINC:
149 detected during a build. For :term:`PR` increments on changes,
154 .. _migration-1.6-variable-changes-IMAGE_TYPES:
[all …]
|
| H A D | migration-2.1.rst | 61 .. _migration-2.1-makefile-environment-changes:
63 Makefile Environment Changes
107 as was previously assumed. Rather, the value changes based on whether
134 or that mention :ref:`ref-tasks-rootfs`, you might need to update those changes.
185 .. _migration-2.1-class-changes:
187 Class Changes
208 .. _migration-2.1-build-system-ui-changes:
210 Build System User Interface Changes
213 The following changes have been made to the build system user interface:
242 .. _migration-2.1-poky-reference-distribution-changes:
[all …]
|
| H A D | migration-2.7.rst | 9 .. _migration-2.7-bitbake-changes:
11 BitBake Changes
14 The following changes have been made to BitBake:
81 .. _migration-2.7-packaging-changes:
83 Packaging Changes
86 This section provides information about packaging changes.
109 images should not see any changes assuming
153 .. _migration-2.7-miscellaneous-changes:
155 Miscellaneous Changes
158 The following miscellaneous changes occurred:
|
| H A D | migration-1.5.rst | 9 .. _migration-1.5-host-dependency-changes:
11 Host Dependency Changes
53 The following changes have been made that relate to BitBake:
82 The following changes have been made to the package QA checks:
106 .. _migration-1.5-directory-layout-changes:
108 Directory Layout Changes
111 The following directory changes exist:
160 The following changes have been made that relate to
189 must be changed. You can find a guide on how to make these changes
206 .. _migration-1.5-images-now-rebuild-only-on-changes-instead-of-every-time:
[all …]
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | intro.rst | 60 to separating source changes.
63 minimal changes to the sources, the released recipes provide a vetted
64 base upon which to layer your changes. Doing so allows you to benefit
100 kernel recipes. Configuration changes can be added in the form of
134 #. *Make Changes to the Kernel Source Code if applicable:* Modifying the
136 if you have to do this, you make the changes to the files in the
147 #. *Make Kernel Configuration Changes if Applicable:* If your situation
151 interactively develop and test the configuration changes you are
152 making to the kernel. Saving changes you make with ``menuconfig``
162 Once you are satisfied with the configuration changes made using
[all …]
|
| /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/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
48 #. *Test Your Changes:* Once you have modified the source code, the
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/Documentation/filesystems/ |
| 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
160 - Changes to the on-disk format of XFS must be described in the ondisk
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
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A 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 …]
|