From: tmhikaru@gmail.com
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.35.6
Date: Tue, 28 Sep 2010 00:45:48 -0400 [thread overview]
Message-ID: <20100928044548.GB12856@roll> (raw)
In-Reply-To: <20100927233956.GA15705@roll>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Mon, Sep 27, 2010 at 07:39:56PM -0400, tmhikaru@gmail.com wrote:
> Greg, I noticed that in the ChangeLogs for 2.6.35.x there were some patches
> for the intel driver which seem to be to my untrained eye an attempt to fix
> Linus' problem talked about in that bug report; The patch that is referenced
> in the bug report contains some things at least that were not applied to the
> tree; since I have no idea what I'm looking at, could you verify for me if
> I'm barking up the right tree here? If I am, I'll try building a clean
> 2.6.35 kernel with that patch applied and see if my problem disappears.
WRT to this patch, it appears I was indeed barking up the wrong tree - it
doesn't apply to 2.6.35 at all. I guess I'll have to start bisecting now.
2.6.35.1 and 2.6.35 clearly have the problem. Just wanted to make it clear
that I'd been mistaken about this before you wasted time digging into it.
Thank you,
Tim McGrath
[-- Attachment #2: Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2010-09-28 4:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 0:36 Linux 2.6.35.6 Greg KH
2010-09-27 0:36 ` Greg KH
2010-09-27 1:00 ` Felipe Contreras
2010-09-27 1:31 ` Greg KH
2010-09-27 17:05 ` Felipe Contreras
2010-09-27 16:32 ` tmhikaru
2010-09-27 17:54 ` Greg KH
2010-09-27 19:09 ` tmhikaru
2010-09-27 19:51 ` Florian Mickler
2010-09-27 23:39 ` tmhikaru
2010-09-28 4:45 ` tmhikaru [this message]
2010-09-28 6:35 ` Florian Mickler
2010-09-28 19:03 ` tmhikaru
2010-09-29 7:29 ` Florian Mickler
2010-09-29 11:02 ` tmhikaru
2010-09-29 11:33 ` Miguel Ojeda
2010-09-29 11:52 ` Florian Mickler
2010-09-29 12:19 ` Florian Mickler
2010-09-30 1:33 ` tmhikaru
2010-09-30 5:29 ` Florian Mickler
2010-09-30 7:38 ` tmhikaru
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=20100928044548.GB12856@roll \
--to=tmhikaru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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