From: jp.francois@cynove.com (jean-philippe francois)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] ARM : omap3 : fix wrong container_of in clock36xx.c
Date: Mon, 10 Jun 2013 10:03:23 +0200 [thread overview]
Message-ID: <CAGGh5h0z3OPPL_jECb1NhENo2OaBqebdTC6r_ddhWKDuuB1Ykg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306061517430.5152@utopia.booyaka.com>
2013/6/6 Paul Walmsley <paul@pwsan.com>:
> On Thu, 6 Jun 2013, jean-philippe francois wrote:
>
>> Does the first version [1] of the patch, that only touch the MSB of
>> the divider also trigger the
>> bug ?
>>
>> [1] https://patchwork.kernel.org/patch/2609681/
>
> That one passes the PM test here. Will take this one for v3.10-rc fixes
> instead, since it fixes a known DSS problem and the original code wasn't
> correct.
>
> Jean, could you work with Mike to come up with a better approach for
> v3.11 or v3.12?
>
Hi,
I am ok to work on it, however could you explain to me what is the
expected output of your PM tests, and how to reproduce them ?
The board I used to test the clock frequency was correct suffered from
heavy handed oscilloscope probing and is currently out of order :(
Jean-Philippe Fran?ois.
>
> - Paul
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-10 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 8:50 [PATCH v2 1/1] ARM : omap3 : fix wrong container_of in clock36xx.c Jean-Philippe Francois
2013-05-31 19:32 ` Mike Turquette
2013-06-03 7:50 ` jean-philippe francois
2013-06-03 9:37 ` Paul Walmsley
2013-06-03 9:36 ` Paul Walmsley
2013-06-05 18:21 ` Paul Walmsley
2013-06-06 7:56 ` jean-philippe francois
2013-06-06 15:31 ` Paul Walmsley
2013-06-10 8:03 ` jean-philippe francois [this message]
2013-06-10 8:15 ` Paul Walmsley
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=CAGGh5h0z3OPPL_jECb1NhENo2OaBqebdTC6r_ddhWKDuuB1Ykg@mail.gmail.com \
--to=jp.francois@cynove.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;
as well as URLs for NNTP newsgroup(s).