tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: bug-bisect: add a note about bisecting -next

Explicitly mention how to bisect -next, as nothing in the kernel tree
currently explains that bisects between -next versions won't work well
and it's better to bisect between mainline and -next.

Co-developed-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/ec19d5fc503ff7db3d4c4ff9e97fff24cc78f72a.1730808651.git.linux@leemhuis.info

authored by

Thorsten Leemhuis and committed by
Jonathan Corbet f5aff6fa b934bc75

+21
+21
Documentation/admin-guide/bug-bisect.rst
··· 108 108 With that the process is complete. Now report the regression as described by 109 109 Documentation/admin-guide/reporting-issues.rst. 110 110 111 + Bisecting linux-next 112 + -------------------- 113 + 114 + If you face a problem only happening in linux-next, bisect between the 115 + linux-next branches 'stable' and 'master'. The following commands will start 116 + the process for a linux-next tree you added as a remote called 'next':: 117 + 118 + git bisect start 119 + git bisect good next/stable 120 + git bisect bad next/master 121 + 122 + The 'stable' branch refers to the state of linux-mainline that the current 123 + linux-next release (found in the 'master' branch) is based on -- the former 124 + thus should be free of any problems that show up in -next, but not in Linus' 125 + tree. 126 + 127 + This will bisect across a wide range of changes, some of which you might have 128 + used in earlier linux-next releases without problems. Sadly there is no simple 129 + way to avoid checking them: bisecting from one linux-next release to a later 130 + one (say between 'next-20241020' and 'next-20241021') is impossible, as they 131 + share no common history. 111 132 112 133 Additional reading material 113 134 ---------------------------