From: Thomas Glanzmann <thomas@glanzmann.de>
To: Ben Skeggs <skeggsb@gmail.com>
Cc: Ben Skeggs <bskeggs@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
nouveau <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness
Date: Tue, 17 Jun 2014 07:46:54 +0200 [thread overview]
Message-ID: <20140617054654.GB9117@glanzmann.de> (raw)
In-Reply-To: <CACAvsv7WVPVE_axXU9MS07DVRsn9DaZ+NF5A+9yYr5XxKWYe3A@mail.gmail.com>
Hello Ben,
> > 8777c5c11764d8336d8270f96778158c34c92108 (which is mentioned as the
> > first bad commit above...) is a tiny commit, so I have no idea what
> > you mean by "too large for your taste".
for example I would not export a symbol and do something else in the
same commit, but would split them up in two. I do the minimum work per
commit without breaking compilation or functionality. That way it is
easier to identify issues later on.
> In any case, I encountered the oops myself earlier (absolutely nothing
> to do with that commit) and fixed it here. I've sent it onto Dave for
> the next -fixes merge, so hopefully it'll help your case too.
Can you please send me your fix. I can reboot my machine remotely, but
only once. That way I can tell you if your fix works, or not.
> I have no idea why gmail doesn't auto-add you to the Cc list on reply
> all.. But.. Done :)
thanks.
Cheers,
Thomas
next prev parent reply other threads:[~2014-06-17 5:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 9:58 Thomas Glanzmann
2014-06-15 23:22 ` [Nouveau] " Ben Skeggs
2014-06-17 5:33 ` Thomas Glanzmann
2014-06-17 5:39 ` Ben Skeggs
2014-06-17 5:40 ` Ben Skeggs
2014-06-17 5:46 ` Thomas Glanzmann [this message]
2014-06-17 6:12 ` Andreas Tscharner
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=20140617054654.GB9117@glanzmann.de \
--to=thomas@glanzmann.de \
--cc=bskeggs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=skeggsb@gmail.com \
/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
Powered by JetHome