From: "Woodruff, Richard" <r-woodruff2@ti.com>
To: Wang Sawsd-A24013 <cqwang@motorola.com>,
Mike Chan <mike@android.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick
Date: Thu, 18 Jun 2009 14:32:10 -0500 [thread overview]
Message-ID: <13B9B4C6EF24D648824FF11BE8967162038E2ACC2E@dlee02.ent.ti.com> (raw)
In-Reply-To: <B00E06E2766C2744B022DE9BAF3C59D53F268F@zmy16exm69.ds.mot.com>
Hi,
> From: Wang Sawsd-A24013 [mailto:cqwang@motorola.com]
> Sent: Thursday, June 18, 2009 2:27 PM
> > >+ str r6, [r4] /* restore old value */
> Richard, I think here it should be: str r5, [r4], not r6.
> I modifed this when I was verifying your patch.
You are correct that was a bug. Thanks.
Regards,
Richard W.
prev parent reply other threads:[~2009-06-18 19:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 22:42 [PATCH -pm 0/2] SDRC tweaks for stuck DLL state machine Kevin Hilman
2009-06-15 22:42 ` [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick Kevin Hilman
2009-06-15 22:42 ` [PATCH -pm 2/2] SDRC: whitespace cleanups in DLL lock code Kevin Hilman
2009-06-17 8:04 ` [PATCH -pm 1/2] SDRC: check for stuck DLL state machine and kick Paul Walmsley
2009-06-18 0:04 ` Woodruff, Richard
2009-06-18 15:03 ` Kevin Hilman
2009-06-18 19:21 ` Woodruff, Richard
2009-06-18 21:06 ` Paul Walmsley
2009-06-20 1:42 ` Woodruff, Richard
2009-06-23 20:05 ` Paul Walmsley
2009-06-23 20:11 ` Woodruff, Richard
2009-06-26 8:45 ` Paul Walmsley
2009-06-26 16:07 ` Woodruff, Richard
[not found] ` <8bb80c380906181142m54f543c2v626849983f4507b4@mail.gmail.com>
2009-06-18 18:55 ` Woodruff, Richard
2009-06-18 19:27 ` Wang Sawsd-A24013
2009-06-18 19:32 ` Woodruff, Richard [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=13B9B4C6EF24D648824FF11BE8967162038E2ACC2E@dlee02.ent.ti.com \
--to=r-woodruff2@ti.com \
--cc=cqwang@motorola.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike@android.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.