From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/4] pata_ninja32: suspend/resume support
Date: Tue, 28 Oct 2008 00:42:02 -0400 [thread overview]
Message-ID: <4906981A.2080301@garzik.org> (raw)
In-Reply-To: <20081017180826.7781.59704.stgit@localhost.localdomain>
Alan Cox wrote:
> From: Alan Cox <alan@redhat.com>
>
> I had assumed that the standard recovery would be sufficient for this
> hardware but it isn't. Fix up the other registers on resume as needed. See
> bug #11735
>
> Signed-off-by: Alan Cox <alan@redhat.com>
> ---
>
> drivers/ata/pata_ninja32.c | 43 ++++++++++++++++++++++++++++++++++---------
> 1 files changed, 34 insertions(+), 9 deletions(-)
applied
patches 2-4 look interesting, but I paused to wait for comments (if
any). They look like material for at least a little bit of a linux-next
time before going upstream, not really 2.6.28-rc1 [at the time] material
IMO...
Jeff
next prev parent reply other threads:[~2008-10-28 4:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 18:08 [PATCH 0/4] Small set of further libata patches Alan Cox
2008-10-17 18:08 ` [PATCH 1/4] pata_ninja32: suspend/resume support Alan Cox
2008-10-28 4:42 ` Jeff Garzik [this message]
2008-10-28 9:37 ` Alan Cox
2008-10-17 18:08 ` [PATCH 2/4] libata: Drain data on errors Alan Cox
2008-10-22 15:46 ` Elias Oltmanns
2008-10-22 16:44 ` Alan Cox
2008-10-27 19:14 ` Mark Lord
2008-10-27 21:54 ` Alan Cox
2008-10-17 18:08 ` [PATCH 3/4] libata: Improve timeout handling Alan Cox
2008-10-22 15:47 ` Elias Oltmanns
2008-10-22 16:04 ` Alan Cox
2008-10-17 18:09 ` [PATCH 4/4] libata: clean up the SFF code for coding style Alan Cox
2008-10-22 15:48 ` Elias Oltmanns
2008-10-22 16:02 ` Alan Cox
2008-10-23 0:35 ` Jeff Garzik
2008-10-28 1:49 ` Tejun Heo
2008-10-28 9:47 ` Elias Oltmanns
2008-10-29 2:05 ` Tejun Heo
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=4906981A.2080301@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@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 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).