Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 24 Aug 2018 16:33:38 +0200
From:   "Matthias B." <matthias@winterdrache.de>
To:     Greg KH <gregkh@linuxfoundation.org>
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: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 24 Aug 2018 16:12:54 +0200
Greg KH <gregkh@linuxfoundation.org> 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