From: linuxzsc@gmail.com (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: imx: check busy bit when START/STOP
Date: Tue, 29 Sep 2009 23:14:42 +0800 [thread overview]
Message-ID: <4e090d470909290814v292487f4l2ff3323bec145def@mail.gmail.com> (raw)
In-Reply-To: <20090929142440.GF32420@sirena.org.uk>
On Tue, Sep 29, 2009 at 10:24 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Sep 29, 2009 at 09:54:05PM +0800, Richard Zhao wrote:
>> On Tue, Sep 29, 2009 at 9:25 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
>> > I think it's generally a good idea to start/stop the clocks when needed
>> > as you do here. It should be an extra patch though.
>
>> You think I should split the patch to three: IBB, reg_dump, clk dis/en ?
>> The idea is good, more easy to revert. but sometimes, I think it make
>> small things too complex.
>
> Keeping small things simple is half the reason for doing this - it's not
> just bisection, it's also the fact that it's much easier to read and
> understand a small patch that does one thing than it is to do the same
> with a large patch which makes several unrelated changes. ?When several
> changes are lumped in together it's harder to see the complete version
> of any one change in isolation and more effort is required to work out
> which goals are being accomplished with any given chunk of the patch.
>
Thank you all!
If you don't have other comments, I will split the patch and send out
again tomorrow.
Thanks
Richard
prev parent reply other threads:[~2009-09-29 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 11:41 [PATCH] i2c: imx: check busy bit when START/STOP Richard Zhao
2009-09-29 13:09 ` Wolfram Sang
2009-09-29 13:25 ` Sascha Hauer
2009-09-29 13:54 ` Richard Zhao
2009-09-29 14:06 ` Sascha Hauer
2009-09-29 23:21 ` Richard Zhao
2009-09-29 14:24 ` Mark Brown
2009-09-29 15:14 ` Richard Zhao [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=4e090d470909290814v292487f4l2ff3323bec145def@mail.gmail.com \
--to=linuxzsc@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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