From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([217.72.192.74]:36575 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726264AbeHXSIg (ORCPT ); Fri, 24 Aug 2018 14:08:36 -0400 Date: Fri, 24 Aug 2018 16:33:38 +0200 From: "Matthias B." To: Greg KH Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: How to report kernel panic in 4.4.x Message-ID: <20180824163338.4bd9db8f@ninja> In-Reply-To: <20180824141254.GB31555@kroah.com> References: <20180824142408.6340d052@ninja> <20180824125950.GA29673@kroah.com> <20180824154344.1c53a68c@ninja> <20180824141254.GB31555@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On Fri, 24 Aug 2018 16:12:54 +0200 Greg KH wrote: > > All of the stable trees are here: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ > you want the linux-4.4.y branch to work off of. > > All of the kernels releases are tagged, so you can start with v4.4.147 > as the good entry for 'git bisect'. I've never used git bisect on the kernel. Can I simply do "make" for each step or do I need to "make mrproper" every time? MSB