Gitiles
Code Review Sign In
gerrit.openbmc.org / premsjha / op-build / refs/heads/gh-pages / . / process / KernelTree.html
blob: 9bd246cd83cea320f2c58d4cffff0852ecde573b [file] [log] [blame]
Deployment Bot (from Travis CI)6d7e6e92021-06-14 19:18:41 +0000[diff] [blame]1
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4
5<html xmlns="http://www.w3.org/1999/xhtml">
6 <head>
7 <meta http-equiv="X-UA-Compatible" content="IE=Edge" />
8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
9 <title>op-build Linux Kernel &#8212; OpenPOWER Firmware v2.6-257-g5b5624c2
10 documentation</title>
11 <link rel="stylesheet" href="../_static/alabaster.css" type="text/css" />
12 <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
13 <script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
14 <script type="text/javascript" src="../_static/jquery.js"></script>
15 <script type="text/javascript" src="../_static/underscore.js"></script>
16 <script type="text/javascript" src="../_static/doctools.js"></script>
17 <link rel="index" title="Index" href="../genindex.html" />
18 <link rel="search" title="Search" href="../search.html" />
19 <link rel="next" title="Building with ci scripts" href="building-with-ci.html" />
20 <link rel="prev" title="Contributing to op-build" href="CONTRIBUTING.html" />
21
22 <link rel="stylesheet" href="../_static/custom.css" type="text/css" />
23
24
25 <meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9" />
26
27 </head><body>
28
29
30 <div class="document">
31 <div class="documentwrapper">
32 <div class="bodywrapper">
33
34
35 <div class="body" role="main">
36
37 <div class="section" id="op-build-linux-kernel">
38<h1>op-build Linux Kernel<a class="headerlink" href="#op-build-linux-kernel" title="Permalink to this headline"></a></h1>
39<p>The skiroot/Petitboot kernel is currently based on the 5.3 series.</p>
40<div class="section" id="submitting-a-patch">
41<h2>Submitting a patch<a class="headerlink" href="#submitting-a-patch" title="Permalink to this headline"></a></h2>
42<p>If you require a patch added to the firmware, follow these steps:</p>
43<ol class="arabic simple">
44<li>Submit your patch upstream. It doesn’t need to be upstream, but it
45should be on it’s way</li>
46<li>Send a pull request or a <code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">format-patch</span></code> formatted patch series
47to <a class="reference external" href="mailto:openpower-firmware&#37;&#52;&#48;lists&#46;ozlabs&#46;org">openpower-firmware<span>&#64;</span>lists<span>&#46;</span>ozlabs<span>&#46;</span>org</a>, and cc <a class="reference external" href="mailto:joel&#37;&#52;&#48;jms&#46;id&#46;au">joel<span>&#64;</span>jms<span>&#46;</span>id<span>&#46;</span>au</a>. Be
48sure to use <code class="docutils literal notranslate"><span class="pre">--suppress-cc=sob</span></code> when generating the patches so we
49don’t spam the community. The current tree is based on 5.1-stable
50(although we will always move to the latest stable kernel ASAP).</li>
51</ol>
52</div>
53<div class="section" id="bug-fixes">
54<h2>Bug fixes<a class="headerlink" href="#bug-fixes" title="Permalink to this headline"></a></h2>
55<p>Whenever a stable release is tagged in
56<a class="reference external" href="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/">https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/</a>,
57we will rebase our patches on top of that and create a new release.</p>
58<p>If you are submitting patches upstream that you want to be included,
59then ensure you cc stable as per the
60<a class="reference external" href="https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/stable_kernel_rules.txt">rules</a>.</p>
61</div>
62<div class="section" id="versioning">
63<h2>Versioning<a class="headerlink" href="#versioning" title="Permalink to this headline"></a></h2>
64<p>Versions are the upstream version number, followed by <code class="docutils literal notranslate"><span class="pre">-openpowerN</span></code>,
65where N is the revision that counts up from 1 for the given upstream
66version number. These versions will be present as tags in the git
67repository hosted at <a class="reference external" href="https://github.com/open-power/linux">https://github.com/open-power/linux</a>.</p>
68<p>We aim to follow “the latest upstream release”.</p>
69<p>For op-build stable trees, we follow the latest stable release of the
70kernel that particular op-build release was made with. Since op-build
71stable releases may outlast how long an upstream kernel is maintain for,
72we will move up the kernel version we use until the next LTS kernel.
73Once on an LTS kernel, an op-build stable release will stick with that
74version.</p>
75</div>
76<div class="section" id="tree-and-patches">
77<h2>Tree and patches<a class="headerlink" href="#tree-and-patches" title="Permalink to this headline"></a></h2>
78<p>The kernel tree hosted at <a class="reference external" href="https://github.com/open-power/linux">https://github.com/open-power/linux</a> contains
79the current release plus a set of patches that we carry. Ideally there
80would be no patches carried, as everything should be upstream.</p>
81<p>We take the commits in this tree between the upstream tag and the
82openpower tag and generate a series of patches that are imported into
83the op-build Buildroot overlay, and placed in
84<a class="reference external" href="https://github.com/open-power/op-build/tree/master/openpower/linux">op-build/openpower/linux</a>.
85op-build then fetches the upstream tarball and applies these patches.
86This way we don’t have to clone an entire tree when doing an op-build
87build.</p>
88<p>All patches are to head upstream <em>first</em>. There is a zero chance that
89op-build will carry kernel patches for any time greater than “until the
90next kernel release”, and even then, only in <em>exceptional</em> circumstances.</p>
91</div>
92<div class="section" id="patches-in-the-tree">
93<h2>Patches in the tree<a class="headerlink" href="#patches-in-the-tree" title="Permalink to this headline"></a></h2>
94<ul class="simple">
95<li>xhci: Reset controller on xhci shutdown</li>
96</ul>
97</div>
98</div>
99
100
101 </div>
102
103 </div>
104 </div>
105 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
106 <div class="sphinxsidebarwrapper">
107<h1 class="logo"><a href="../index.html">OpenPOWER Firmware</a></h1>
108
109
110
111
112
113
114
115
116<h3>Navigation</h3>
117<p class="caption"><span class="caption-text">Contents:</span></p>
118<ul class="current">
119<li class="toctree-l1"><a class="reference internal" href="../introduction.html">Introduction to OpenPOWER Firmware</a></li>
120<li class="toctree-l1"><a class="reference internal" href="../testing.html">Testing op-build</a></li>
121<li class="toctree-l1 current"><a class="reference internal" href="index.html">Development Process</a><ul class="current">
122<li class="toctree-l2"><a class="reference internal" href="CONTRIBUTING.html">Contributing to op-build</a></li>
123<li class="toctree-l2 current"><a class="current reference internal" href="#">op-build Linux Kernel</a></li>
124<li class="toctree-l2"><a class="reference internal" href="building-with-ci.html">Building with ci scripts</a></li>
125<li class="toctree-l2"><a class="reference internal" href="stable-rules.html">op-build stable tree rules and releases</a></li>
126</ul>
127</li>
128<li class="toctree-l1"><a class="reference internal" href="../boot-devices.html">Supported Boot Devices</a></li>
129<li class="toctree-l1"><a class="reference internal" href="../versioning.html">Version Scheme</a></li>
130<li class="toctree-l1"><a class="reference internal" href="../release-notes/index.html">op-build Release Notes</a></li>
131</ul>
132
133<div class="relations">
134<h3>Related Topics</h3>
135<ul>
136 <li><a href="../index.html">Documentation overview</a><ul>
137 <li><a href="index.html">Development Process</a><ul>
138 <li>Previous: <a href="CONTRIBUTING.html" title="previous chapter">Contributing to op-build</a></li>
139 <li>Next: <a href="building-with-ci.html" title="next chapter">Building with ci scripts</a></li>
140 </ul></li>
141 </ul></li>
142</ul>
143</div>
144<div id="searchbox" style="display: none" role="search">
145 <h3>Quick search</h3>
146 <div class="searchformwrapper">
147 <form class="search" action="../search.html" method="get">
148 <input type="text" name="q" />
149 <input type="submit" value="Go" />
150 <input type="hidden" name="check_keywords" value="yes" />
151 <input type="hidden" name="area" value="default" />
152 </form>
153 </div>
154</div>
155<script type="text/javascript">$('#searchbox').show(0);</script>
156
157
158
159
160
161
162
163
164 </div>
165 </div>
166 <div class="clearer"></div>
167 </div>
168 <div class="footer">
169 &copy;2017, OpenPOWER Foundation System Software Work Group.
170
171 |
172 Powered by <a href="http://sphinx-doc.org/">Sphinx 1.7.9</a>
173 &amp; <a href="https://github.com/bitprophet/alabaster">Alabaster 0.7.12</a>
174
175 |
176 <a href="../_sources/process/KernelTree.rst.txt"
177 rel="nofollow">Page source</a>
178 </div>
179
180
181
182
183 </body>
184</html>