From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
sean@poorly.run, airlied@linux.ie
Subject: Re: Kernel panic during drm/nouveau init 5.3.0-rc7-next-20190903
Date: Mon, 9 Sep 2019 13:24:49 +0300 [thread overview]
Message-ID: <CAJ1xhMXKNRfOm1Xj3B_cgLByBfDP03P+DBEbRpWc+tU6kdxtBw@mail.gmail.com> (raw)
In-Reply-To: <20190909202128.0c420ddd@canb.auug.org.au>
On Mon, Sep 9, 2019 at 1:21 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi,
>
> On Mon, 9 Sep 2019 20:11:59 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > If you are bisecting linux-next, I will suggest bisecting between the
> > stable branch on linux-next (which is just Linus' tree when I started
> > that day) and the top of the first linux-next that fails. (Assuming
> > that the stable branch is good).
>
> Actually (since you won't be bisecting the latest linux-next), you
> probably want to use
>
> git merge-base stable next-20190903
> (or whatever linux-next you are bisecting)
>
> as your first good commit (assuming it id good :-)).
>
> --
> Cheers,
> Stephen Rothwell
Hi Stephen,
Thanks very much for the tips.
I'll go ahead and give those a try.
next prev parent reply other threads:[~2019-09-09 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 9:05 Kernel panic during drm/nouveau init 5.3.0-rc7-next-20190903 Alexander Kapshuk
2019-09-07 10:32 ` Daniel Vetter
2019-09-08 14:13 ` Alexander Kapshuk
2019-09-09 10:11 ` Stephen Rothwell
2019-09-09 10:21 ` Stephen Rothwell
2019-09-09 10:24 ` Alexander Kapshuk [this message]
2019-09-13 17:19 ` Daniel Vetter
2019-09-20 19:44 ` Alexander Kapshuk
2019-09-20 19:48 ` Daniel Vetter
2019-09-23 6:38 ` Gerd Hoffmann
2019-09-23 6:50 ` Alexander Kapshuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ1xhMXKNRfOm1Xj3B_cgLByBfDP03P+DBEbRpWc+tU6kdxtBw@mail.gmail.com \
--to=alexander.kapshuk@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sean@poorly.run \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).