Lines Matching full:latest
25 Find the latest rendered version of this text here:
81 * **Segment 1**: build a kernel from the latest mainline codebase.
87 a) Checking out latest mainline code::
241 :ref:`Segment 1: try to reproduce the problem with the latest codebase <introlatestcheck_bissbs>`.
260 the latest 'mainline' kernel (e.g. versions like 6.0, 6.1-rc1, or 6.1-rc6),
523 * Reprocess the .config after the latest adjustments and store it in a safe
533 Segment 1: try to reproduce the problem with the latest codebase
543 * Check out the latest Linux codebase.
548 latest version ('linux-6.1.y' in the following example)::
663 the regression with it? Then you should test the latest mainline codebase as
793 In case you skipped the 'test latest codebase' step in the guide, check its
858 * Try reverting the culprit on top of latest mainline to see if this fixes your
868 Begin by checking out the latest codebase depending on the range you bisected:
872 latest codebase for the affected series like this::
877 * In all other cases check out latest mainline::
937 beforehand (e.g. to test the latest codebase and the version considered
965 * Could you initially reproduce the regression with the latest codebase and
967 top of the latest codebase? Then you want to keep those two kernels around
976 for some time: the one built from the latest codebase, the one created from
991 * Update your Git clone and check out the latest code.
993 * In case you want to test mainline, fetch its latest changes before checking
1005 Then fetch the latest changes and check out the latest version from the
1017 * In case you just want to test the latest codebase, head to the next step,
1320 First, execute the following command to retrieve the latest mainline codebase::
1573 *Reprocess the .config after the latest changes and store it in a safe place.*
1587 Try to reproduce the problem with the latest codebase
1591 still occurs with the latest codebase.* [:ref:`... <introlatestcheck_bissbs>`]
1593 For some readers it might seem unnecessary to check the latest codebase at this
1614 * If the cause for your regression was already fixed in the latest mainline
1641 Check out the latest Linux codebase
1644 *Check out the latest Linux codebase.*
1821 the kernel you built from the latest codebase. These are the most frequent:
1840 Check the kernel built from the latest stable/longterm codebase
1844 reproduce it with the kernel you just built using the latest mainline sources?
1845 Then check if the latest codebase for the particular series might already fix
1911 to build another kernel from the latest codebase, as your earlier tests with
1912 mainline and the latest version from an affected stable/longterm series were
2008 *Try reverting the culprit on top of the latest codebase to see if this fixes