From: Greg KH <gregkh@suse.de>
To: David Engel <david@istwok.net>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: Linux 2.6.27.16
Date: Thu, 12 Feb 2009 19:29:58 -0800 [thread overview]
Message-ID: <20090213032958.GA4474@suse.de> (raw)
In-Reply-To: <20090213032550.GB3721@opus.istwok.net>
On Thu, Feb 12, 2009 at 09:25:50PM -0600, David Engel wrote:
> On Thu, Feb 12, 2009 at 05:29:55PM -0800, Greg KH wrote:
> > On Thu, Feb 12, 2009 at 05:14:04PM -0800, Greg KH wrote:
> > > On Thu, Feb 12, 2009 at 05:08:27PM -0800, Greg KH wrote:
> > > > > It seems that dev->platform_data is NULL on my system.
> > > >
> > > > Not good, let me dig to see if I missed a patch...
> > >
> > > Ok, I did.
> > >
> > > If you apply the patch below, does the oops go away?
>
> 3 or 4 chunks failed to apply and the ones that did apply were offset
> by several lines. If you'd like, I can try to apply it by hand and
> test it tomorrow.
No, I thought better of it after looking at the code :)
> > > But that's not really a "stable" fix, so I guess I'll just go revert the
> > > problem patch. Let me go make that fix...
> >
> > Ok, I reverted the problem patch and released 2.6.27.17. Please let me
> > know if you still have a problem with that kernel release.
>
> I'm building 2.6.27.17 now, but I expect it to work since reverting
> that one patch is all I did to get 2.6.27.16 working for me.
Yeah, that's what I'm more concerned about.
thanks,
greg k-h
next prev parent reply other threads:[~2009-02-13 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 18:04 Linux 2.6.27.16 Greg KH
2009-02-12 18:05 ` Greg KH
2009-02-12 23:01 ` David Engel
2009-02-13 1:08 ` Greg KH
2009-02-13 1:14 ` Greg KH
2009-02-13 1:29 ` Greg KH
2009-02-13 3:25 ` David Engel
2009-02-13 3:29 ` Greg KH [this message]
2009-02-13 3:46 ` David Engel
2009-02-13 4:07 ` Greg KH
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=20090213032958.GA4474@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@istwok.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.