From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 1/1] imx51.dtsi: fix PATA device clock
Date: Sat, 07 Sep 2013 17:36:11 +0400 [thread overview]
Message-ID: <522B2BCB.1050209@cogentembedded.com> (raw)
In-Reply-To: <20130907132507.353801753@rtp-net.org>
Hello.
On 07-09-2013 17:23, Arnaud Patard (Rtp) wrote:
Why you sent the patch as attachment?
> Commit 718a35006f3fa48540d69bd649ff76ea4cdc1ef2 adds pata support to the
> imx51.dtsi file and is using clock 161. The problem is that the right clock
> is 172, according to 5d530bb0ad84d403d1aac79a8a8acf2c2b0a8dd7.
Please specify those commits' summaries in paren
> Using the clock 172 makes things work again (and kills a nasty system freeze)
> Tested-by: Steve Klimaszewski<steev@gentoo.org>
> Signed-off-by: Arnaud Patard<arnaud.patard@rtp-net.org>
WBR, Sergei
next prev parent reply other threads:[~2013-09-07 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 13:23 [patch 1/1] imx51.dtsi: fix PATA device clock Arnaud Patard (Rtp)
2013-09-07 13:32 ` Steev Klimaszewski
2013-09-07 13:36 ` Sergei Shtylyov [this message]
2013-09-09 14:41 ` Shawn Guo
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=522B2BCB.1050209@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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