Searched full:upstream (Results 1 – 25 of 113) sorted by relevance
12345
| /Documentation/driver-api/cxl/ |
| D | access-coordinates.rst | 8 Shared Upstream Link Calculation
12 the endpoints behind a switch being more than the switch upstream link.
13 A similar situation can occur within the host, upstream of the root ports.
16 upstream link being a limiting factor in mind.
47 Min(SW 0 Upstream Link to RP0 BW,
48 Min(SW0SSLBIS for SW0DSP0 (EP0), EP0 DSLBIS, EP0 Upstream Link) +
49 Min(SW0SSLBIS for SW0DSP1 (EP1), EP1 DSLBIS, EP1 Upstream link)) +
50 Min(SW 1 Upstream Link to RP1 BW,
51 Min(SW1SSLBIS for SW1DSP0 (EP2), EP2 DSLBIS, EP2 Upstream Link) +
52 Min(SW1SSLBIS for SW1DSP1 (EP3), EP3 DSLBIS, EP3 Upstream link))) +
[all …]
|
| /Documentation/process/ |
| D | contribution-maturity-model.rst | 19 take on upstream contributions such as reviewing other people’s patches,
24 expectations for upstream community engagement aim to increase the
35 upstream community.
58 * A Software Engineer’s upstream code contributions will be considered
78 * The number of upstream kernel contributions by team or organization
80 * The percentage of kernel developers who have made upstream
84 and/or products, and the publication date of the upstream kernel
92 time focused on Upstream Work, which is defined as reviewing patches,
94 such as writing or maintaining tests, upstream tech debt reduction,
104 * Upstream kernel development is considered a formal job position, with
[all …]
|
| D | stable-kernel-rules.rst | 9 - It or an equivalent fix must already exist in Linux mainline (upstream).
155 to. When doing so, you must note the upstream commit ID in the changelog of your
158 commit <sha1> upstream.
162 [ Upstream commit <sha1> ]
164 If the submitted patch deviates from the original upstream patch (for example
|
| D | backporting.rst | 80 commit <upstream commit> upstream
84 [ Upstream commit <upstream commit> ]
464 places exist upstream -- if they don't, it's likely the patch may need
469 If you do find other instances of the same pattern in the upstream tree
484 colordiff -yw -W 200 <(git diff -W <upstream commit>^-) <(git diff -W HEAD^-) | less -SR
567 [ Upstream commit <mainline rev> ]
573 The "Upstream commit" line is sometimes slightly different depending on
576 commit <mainline rev> upstream.
|
| /Documentation/translations/sp_SP/process/ |
| D | contribution-maturity-model.rst | 24 upstream, como revisar los parches de otras personas, reestructurar la
29 expectativas comunes para la participación con la comunidad upstream
41 upstream.
63 * Las contribuciones de código upstream de un ingeniero de software se
84 * El número de contribuciones al kernel upstream por equipo u
88 contribuciones upstream relativo al total de desarrolladores
92 upstream en el que se basa el kernel interno.
103 de tecnología upstream, escribir documentación, etc.
112 * El desarrollo del kernel upstream se considera un puesto de trabajo
119 de trabajo upstream a trabajo enfocado en perseguir directamente los
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 68 newer base or avoiding a merge with an upstream repository is not
102 required before any given branch finds its way into an upstream repository.
127 requests, and upstream maintainers should verify the tags when pulling
135 Merging from sibling or upstream trees
139 trees tend to be a red flag when it comes time to push a branch upstream.
152 you are managing is stable and ready for upstream. Frequent merges can
160 Even then, you should not back merge a tree above your immediate upstream
161 tree; if a higher-level back merge is really required, the upstream tree
165 maintainer merges with the upstream in order to resolve merge conflicts
185 asking upstream to do.
[all …]
|
| D | messy-diffstat.rst | 8 process of sending work upstream. Normally, the result includes a nice
73 upstream is a well-known way to get a grumpy response.
96 shows what is really going on. That request can then be sent upstream.
|
| /Documentation/kbuild/ |
| D | gcc-plugins.rst | 39 compiler features that are neither in GCC nor Clang upstream. Once
40 their utility is proven, the goal is to upstream the feature into GCC
45 upstream compiler support (in either GCC or Clang).
48 bring the feature to upstream GCC (rather than just as a kernel-specific
53 to upstream the feature to GCC (and Clang).
55 After a feature is available in upstream GCC, the plugin will be made
|
| /Documentation/scsi/ |
| D | lpfc.rst | 11 toward the upstream kernel. As such, we removed #ifdefs for older kernels
16 and extended attribute support is now part of the upstream kernel
27 history of the driver as we push for upstream acceptance.
67 This source package is targeted for the upstream kernel only. (See notes
|
| /Documentation/devicetree/bindings/sound/ |
| D | mrvl,pxa-ssp.txt | 6 port A phandle reference to a PXA ssp upstream device
18 /* upstream device */
|
| /Documentation/gpu/rfc/ |
| D | i915_gem_lmem.rst | 5 Upstream plan
7 For upstream the overall plan for landing all the DG1 stuff and turning it for
|
| /Documentation/PCI/ |
| D | pcieaer-howto.rst | 145 default reset_link function, but different Upstream Ports might
147 Upstream Port drivers may provide their own reset_link functions.
181 at upstream is not required. The AER driver calls error_detected(dev,
185 Endpoint <==> Downstream Port B <==> Upstream Port A <==> Root Port
187 If Upstream Port A captures an AER error, the hierarchy consists of
196 a hierarchy in question. Then, performing link reset at upstream is
218 What happens if an upstream port service driver does not provide
223 upstream ports who are attached by the service driver.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-atr.yaml | 14 ("upstream") port and N I2C master child ("downstream") ports, and
15 forwards transactions from upstream to the appropriate downstream port
|
| D | i2c-mux-ltc4306.txt | 26 - ltc,upstream-accelerators-enable: Enables the rise time accelerators
27 on the upstream port.
|
| D | i2c-mux-pca954x.yaml | 77 isolated from the upstream bus. If not set all channels are isolated from
78 the upstream bus until the fault is cleared.
89 channel is isolated from the upstream bus.
|
| /Documentation/driver-api/acpi/ |
| D | linuxized-acpica.rst | 18 upstream.
169 Figure 2. ACPICA -> Linux Upstream Process
198 the ACPICA code in Linux and the upstream ACPICA code, referred to as
210 upstream source code and generate the linuxized fix using the ACPICA
215 Those changes may not be acceptable by ACPICA upstream and in such cases
223 fixups are backported to the upstream ACPICA sources, they must follow
224 the upstream ACPICA rules and so further modifications may appear.
235 This paragraph guides Linux developers to use the ACPICA upstream release
236 utilities to obtain Linux patches corresponding to upstream ACPICA commits
273 If you have local copies of both Linux and upstream ACPICA, you can generate
|
| /Documentation/features/ |
| D | arch-support.txt | 4 support matrix, for all upstream Linux architectures.
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 10 patch acceptance and upstream merge. Patches are merged to either the
32 Those tests need to be passed before the patches go upstream, but not
|
| /Documentation/arch/openrisc/ |
| D | todo.rst | 5 The OpenRISC Linux port is fully functional and has been tracking upstream
|
| /Documentation/networking/ |
| D | phy-link-topology.rst | 48 its SFP upstream ops.
90 upstream is phylink (so, no media-converter).
92 PHY drivers that can be used as SFP upstream need to call :c:func:`phy_sfp_attach_phy`
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-fuse | 21 may be passed to fuse-bpf. For upstream bpf program types, this
|
| /Documentation/translations/zh_CN/maintainer/ |
| D | modifying-patches.rst | 40 commit 1c40279960bcd7d52dbdf1d466b20d24b99176c8 upstream.
|
| /Documentation/devicetree/bindings/arm/ |
| D | google.yaml | 16 Currently upstream this is devices using "gs101" SoC which is found in Pixel
|
| /Documentation/arch/arc/ |
| D | arc.rst | 18 ARC processors. Some of the projects are forks of various upstream projects,
19 where "work in progress" is hosted prior to submission to upstream projects.
|
| /Documentation/gpu/amdgpu/display/ |
| D | index.rst | 28 When we upstream a new feature or some patches, we pack them in a patchset with
67 #. Regarding IGT, we use the latest code from the upstream.
|
12345