From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: alan@lxorguk.ukuu.org.uk, albertcc@tw.ibm.com, uchang@tw.ibm.com,
forrest.zhao@intel.com, brking@us.ibm.com,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 9/20] libata: reimplement LLD init_one()'s using new init helpers
Date: Tue, 19 Sep 2006 15:11:19 +0900 [thread overview]
Message-ID: <450F8A07.4090604@gmail.com> (raw)
In-Reply-To: <450F8326.7090108@pobox.com>
Helloooo,
Jeff Garzik wrote:
> Unfortunately, while this patch seems correct, it is also difficult to
> review, and I'm thinking it reflects that another approach may need to
> be considered.
>
> Usually the drivers and API are often change in small chunks, whereas
> this patchset is more along the lines of
> 1) add new helpers
> 2) update everything to use new helpers
> 3) delete old helpers
>
> The previous approach was closer to
> * small update to API & drivers
> * small update to API & drivers
> * small update to API & drivers
> ...
>
> I recognize that we are changing the LLDD init model, but I bet if you
> think really hard, you could come up with a less-drastic transition path.
This patchset has been one of the most painful to carry around due to
dependencies on everything and the wide range of changes. I agree that
there can be a better way to split this patch if I think *really* hard,
but was kind of hoping I could avoid that. :-)
I'll try to reshuffle the whole set as you suggested but I can't say for
sure. Please note that lots of previous EH changes were done this way -
implement new framework while leaving old one alone, convert LLDs, kill
old framework. I have to admit that this patchset is more drastic tho.
Thanks.
--
tejun
prev parent reply other threads:[~2006-09-19 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11559779721014-git-send-email-htejun@gmail.com>
2006-09-19 5:41 ` [PATCH 9/20] libata: reimplement LLD init_one()'s using new init helpers Jeff Garzik
2006-09-19 6:11 ` Tejun Heo [this message]
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=450F8A07.4090604@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=brking@us.ibm.com \
--cc=forrest.zhao@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=uchang@tw.ibm.com \
/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.