public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-nospam@schottelius.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nico Schottelius <nico-linux-20100709@schottelius.org>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues)
Date: Wed, 8 Sep 2010 08:21:42 +0200	[thread overview]
Message-ID: <20100908062141.GA2813@schottelius.org> (raw)
In-Reply-To: <201009080128.52849.rjw@sisk.pl>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

Rafael J. Wysocki [Wed, Sep 08, 2010 at 01:28:52AM +0200]:
> On Wednesday, September 08, 2010, Nico Schottelius wrote:
> > Rafael J. Wysocki [Tue, Sep 07, 2010 at 11:48:41PM +0200]:
> > > On Tuesday, September 07, 2010, Jeff Chua wrote:
> > > > 
> > > > Cool. Thanks for the short-cut! At least now, I can resume, but got a
> > > > lot of BUGS showing up upon resume after applying the patch.
> > > 
> > > This also was reported IIRC, but there's no resolution so far.  It's a
> > > different issue.
> > 
> > Can somebody ping me, as soon as a git pull on linux-2.6
> > should be as "stable" (or more stable) than 2.6.34?
> 
> No one can say when that happens for your machine.

True. I was more wondering, when the bisected issue will
be fixed, as this may give my machine some more chances
to work on Linux.

Btw, do you also recognize a different pattern on LKML?

In the past it was mostly "$device not support" && wait
for third party patch to go into upstream, whereas today
it "should be supported", but crashes/freezes sometimes.

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-09-08  6:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 17:04 2.6.35-rc4 / X201 issues Nico Schottelius
2010-07-09 17:29 ` Jesse Barnes
2010-09-06  7:17   ` 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues) Nico Schottelius
2010-09-06  8:49     ` Nico Schottelius
2010-09-06 13:50     ` Jeff Chua
2010-09-06 18:37       ` Rafael J. Wysocki
2010-09-07  3:42         ` Jeff Chua
2010-09-07 21:48           ` Rafael J. Wysocki
2010-09-07 22:50             ` Nico Schottelius
2010-09-07 23:28               ` Rafael J. Wysocki
2010-09-08  6:21                 ` Nico Schottelius [this message]
2010-09-08 22:27                   ` Rafael J. Wysocki
2010-09-10  8:26                 ` Nico Schottelius
  -- strict thread matches above, loose matches on Subject: below --
2010-09-10  5:36 Jeff Chua
2010-09-10  7:48 ` Peter Zijlstra
2010-09-10 11:53   ` Jeff Chua
2010-09-10 12:05     ` Peter Zijlstra
2010-09-10 17:19       ` Jeff Chua

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=20100908062141.GA2813@schottelius.org \
    --to=nico-nospam@schottelius.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-linux-20100709@schottelius.org \
    --cc=rjw@sisk.pl \
    /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