linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	roppedisano@infracomspa.it, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org, rjw@sisk.pl,
	linux-acpi@vger.kernel.org
Subject: Re: libata: cdrw/dvdrom disabed after s2ram (2.6.24-rc2)
Date: Thu, 8 Nov 2007 18:22:18 +0000	[thread overview]
Message-ID: <20071108182217.GA2685@srcf.ucam.org> (raw)
In-Reply-To: <20071108101341.6c4f88d4.akpm@linux-foundation.org>

On Thu, Nov 08, 2007 at 10:13:41AM -0800, Andrew Morton wrote:

> I suspect it wold be best to disable the feature for the 2.6.24 release,
> then reenable it afterwards and keep doing this until the code is
> sufficiently stable.

GTF method execution failure currently looks like it's fatal, when it 
probably shouldn't be. I'll send a patch shortly.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2007-11-08 18:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4731C86B.1040704@infracomspa.it>
2007-11-07 20:13 ` libata: cdrw/dvdrom disabed after s2ram (2.6.24-rc2) Andrew Morton
2007-11-08 16:43   ` Roberto Oppedisano
2007-11-08 17:49     ` Andrew Morton
2007-11-08 18:02       ` Jeff Garzik
2007-11-08 18:13         ` Andrew Morton
2007-11-08 18:19           ` Jeff Garzik
2007-11-08 19:02             ` Andrew Morton
2007-11-08 19:49               ` Mark Lord
2007-11-08 19:58                 ` Andrew Morton
2007-11-08 18:22           ` Matthew Garrett [this message]
2007-11-08 18:37             ` [PATCH] Don't fail ata device revalidation for bad _GTF methods Matthew Garrett
2007-11-09 12:29               ` Roberto Oppedisano
2007-11-10  5:32               ` Jeff Garzik
2007-11-09 15:48         ` libata: cdrw/dvdrom disabed after s2ram (2.6.24-rc2) Roberto Oppedisano

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=20071108182217.GA2685@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=roppedisano@infracomspa.it \
    /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;
as well as URLs for NNTP newsgroup(s).