All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: Hannes Reinecke <hare@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] Fixup ahci suspend / resume
Date: Tue, 28 Feb 2006 10:22:42 -0500	[thread overview]
Message-ID: <44046AC2.1060002@pobox.com> (raw)
In-Reply-To: <20060228151928.GC24981@suse.de>

Jens Axboe wrote:
> Upstream 2.6.x certainly _does_ care about suspend/resume! To me, this
> patch seems simple enough to be included. It's little more than
> splitting the register init out form the port_stop/start functions and
> calling them on resume/suspend appropriately.

Upstream _libata_ doesn't care much about suspend/resume.  Officially, 
its a work in progress with major pieces -- your patch and ACPI -- still 
missing.

Further, good improvements covering some of the changes in Hannes' patch 
are already in #upstream.

Thus, it's more work than its worth to care about the patch as-is.  It 
should be redone against #upstream, which is where all suspend/resume 
development is occurring.

	Jeff



  reply	other threads:[~2006-02-28 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 14:35 [PATCH] Fixup ahci suspend / resume Hannes Reinecke
2006-02-28 14:45 ` Mark Lord
2006-02-28 14:59   ` Hannes Reinecke
2006-02-28 15:14 ` Jeff Garzik
2006-02-28 15:19   ` Jens Axboe
2006-02-28 15:22     ` Jeff Garzik [this message]
2006-02-28 15:28       ` Jens Axboe
2006-02-28 15:35         ` Jeff Garzik
2006-02-28 15:57           ` Hannes Reinecke
2006-02-28 17:25             ` Jens Axboe
2006-03-04  7:37               ` Randy.Dunlap
2006-03-06  8:36                 ` Hannes Reinecke

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=44046AC2.1060002@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=hare@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --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 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.