From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0108/1529] Fix typo
Date: Fri, 10 Jun 2016 04:18:55 -0700 [thread overview]
Message-ID: <20160610111855.GZ22406@atomide.com> (raw)
In-Reply-To: <20160521115032.4966-1-andrea.gelmini@gelma.net>
* Andrea Gelmini <andrea.gelmini@gelma.net> [160521 04:52]:
> --- a/arch/arm/mach-omap2/sdrc.h
> +++ b/arch/arm/mach-omap2/sdrc.h
> @@ -175,8 +175,8 @@ u32 omap2xxx_sdrc_reprogram(u32 level, u32 force);
> * don't adjust it down as your clock period increases the refresh interval
> * will not be met. Setting all parameters for complete worst case may work,
> * but may cut memory performance by 2x. Due to errata the DLLs need to be
> - * unlocked and their value needs run time calibration. A dynamic call is
> - * need for that as no single right value exists acorss production samples.
> + * unlocked and their value needs run time calibration. A dynamic call is
> + * need for that as no single right value exists across production samples.
Applying patches 102 - 108 into omap-for-v4.8/soc thanks.
Tony
prev parent reply other threads:[~2016-06-10 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 11:50 [PATCH 0108/1529] Fix typo Andrea Gelmini
2016-05-21 12:00 ` Ivaylo Dimitrov
2016-06-10 11:18 ` Tony Lindgren [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=20160610111855.GZ22406@atomide.com \
--to=tony@atomide.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).