From: Jeff Garzik <jgarzik@pobox.com>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: htejun@gmail.com, hare@suse.de, axboe@suse.de, linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/6] AHCI suspend/resume support --take4
Date: Wed, 12 Jul 2006 13:42:54 -0400 [thread overview]
Message-ID: <44B5349E.3070802@pobox.com> (raw)
In-Reply-To: <1152599802.7132.290.camel@forrest26.sh.intel.com>
zhao, forrest wrote:
> Hi, all
>
> This is resend of the take 4 of AHCI suspend/resume patches.
> The patch is against libata #upstream.
>
> Compared with last version, all the changes are in [PATCH 6/6]. In
> particular, I made changes to the sixth patch to integrate it with
> Tejun's PM patch.
My current, still-pending request for these patches:
Please split up the patches such that each individual patch -- when
applied in succession, creates a compilable, usable driver. Patch #1
must producing a working driver. Patches #1-2 must produce a working
driver. Patches #1-3 must produce a working driver. Patches #2-3
(without patch #1) need not apply, much less produce a working driver.
As I described in an earlier email, patches are like mathematical
proofs: each step must produce a "complete equation."
For example, patch #1 in this series looks OK -- if only the existing
users of ahci_stop_engine() and ahci_start_engine() to work.
As another example, the ACPI patches need to be split up into logical
chunks, probably just two patches:
1) Add support necessary to utilize _SDD, _GTF (SATA)
2) Add support necessary to utilize _GTM, _STM (PATA)
or perhaps three patches:
1) _GTF support, basic ACPI support
2) SATA support (_SDD, other SATA details)
3) PATA support (_GTM, _STM, other PATA details)
Overall, your code changes are looking good, but are not split up in a
usable manner.
Regards,
Jeff
next prev parent reply other threads:[~2006-07-12 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 6:36 [PATCH 0/6] AHCI suspend/resume support --take4 zhao, forrest
2006-07-12 17:42 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-10 3:33 zhao, forrest
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=44B5349E.3070802@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=forrest.zhao@intel.com \
--cc=hare@suse.de \
--cc=htejun@gmail.com \
--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).