From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jens Axboe <axboe@suse.de>
Cc: hare@suse.de, jgarzik@pobox.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] Fixup ahci suspend / resume
Date: Fri, 3 Mar 2006 23:37:16 -0800 [thread overview]
Message-ID: <20060303233716.67ffaff6.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060228172542.GF24981@suse.de>
On Tue, 28 Feb 2006 18:25:43 +0100 Jens Axboe wrote:
> On Tue, Feb 28 2006, Hannes Reinecke wrote:
> > Jeff Garzik wrote:
> > > Jens Axboe wrote:
> > >> I'm sure Hannes will regenerate against upstream as well if necessary,
> > >> however that depends on when this should be applied.
> > >
> > > It's far too late and too intrusive for 2.6.16-rc.
> > >
> > > It's #upstream or <null>.
> > >
> > Calm down. Of course I will regenerate is against #upstream.
> > In fact, I've done so initially but wasn't sure what the status of
> > libata-dev is. So I've diffed it against linux-git instead.
> >
> > Updated patch to follow.
>
> Thanks Hannes. I wasn't so much worried about it going directly in (I
> have no problem waiting), just that there seemed to be some disagreement
> on where suspend is at and what we can "support".
Hi Hannes,
Did you ever send the updated patch? I need it to use with the
rest of the ata-acpi objects patchset for #upstream (actually for -mm).
Thanks,
---
~Randy
next prev parent reply other threads:[~2006-03-04 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 14:35 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
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 [this message]
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=20060303233716.67ffaff6.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=axboe@suse.de \
--cc=hare@suse.de \
--cc=jgarzik@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®