From: Paul Dickson <paul@permanentmail.com>
To: Dave Jones <davej@redhat.com>
Cc: sanjoy@mrao.cam.ac.uk, rjw@sisk.pl, linux-kernel@vger.kernel.org
Subject: Re: Bisects that are neither good nor bad
Date: Tue, 30 May 2006 19:45:09 -0700 [thread overview]
Message-ID: <20060530194509.80a7891b.paul@permanentmail.com> (raw)
In-Reply-To: <20060529145255.GB32274@redhat.com>
On Mon, 29 May 2006 10:52:55 -0400, Dave Jones wrote:
> The SATA fix Mark proposed also didn't improve the situation for me :-/
Fedora kernel 2230 is supposed to include the patch, yet resuming doesn't
work with that kernel.
-Paul
next prev parent reply other threads:[~2006-05-31 2:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 21:02 Resume stops working between 2.6.16 and 2.6.17-rc1 on Dell Inspiron 6000 Paul Dickson
2006-05-28 21:08 ` Bisects that are neither good nor bad Paul Dickson
2006-05-28 21:24 ` Rafael J. Wysocki
2006-05-28 21:34 ` Dave Jones
2006-05-29 11:37 ` Sanjoy Mahajan
2006-05-29 14:52 ` Dave Jones
2006-05-30 15:29 ` Pavel Machek
2006-06-03 8:58 ` Rafael J. Wysocki
2006-06-03 9:11 ` Russell King
2006-06-09 8:38 ` Pavel Machek
2006-06-09 8:42 ` Russell King
2006-06-09 8:46 ` fixing serial console over suspend [was Re: Bisects that are neither good nor bad] Pavel Machek
2006-06-09 8:51 ` Russell King
2006-06-11 14:08 ` Bisects that are neither good nor bad Russell King
2006-05-31 2:45 ` Paul Dickson [this message]
2006-05-28 22:02 ` Paul Dickson
2006-05-29 0:12 ` Paul Dickson
2006-05-28 21:11 ` Resume stops working between 2.6.16 and 2.6.17-rc1 on Dell Inspiron 6000 Arjan van de Ven
2006-05-28 21:29 ` Paul Dickson
2006-05-28 21:49 ` Mark Lord
2006-05-29 0:21 ` Paul Dickson
2006-05-29 0:40 ` Andrew Morton
2006-05-29 1:47 ` Paul Dickson
2006-05-29 3:02 ` Mark Lord
2006-05-29 15:12 ` Pavel Machek
2006-05-31 2:38 ` Paul Dickson
2006-05-29 3:03 ` Mark Lord
2006-05-29 22:56 Bisects that are neither good nor bad linux
2006-05-30 0:46 ` Linus Torvalds
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=20060530194509.80a7891b.paul@permanentmail.com \
--to=paul@permanentmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sanjoy@mrao.cam.ac.uk \
/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