From: Mark Brown <broonie@kernel.org>
To: Aaron Brice <aaron.brice@datasoft.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, stefan@agner.ch
Subject: Re: [PATCH 1/2] spi: fsl-dspi: Fix clock rate scale values
Date: Fri, 27 Mar 2015 19:33:36 -0700 [thread overview]
Message-ID: <20150328023336.GL1743@sirena.org.uk> (raw)
In-Reply-To: <1427493103-7354-2-git-send-email-aaron.brice@datasoft.com>
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
On Fri, Mar 27, 2015 at 02:51:42PM -0700, Aaron Brice wrote:
> Update baud rate scaling algorithm to get better scaling values.
Can we have a better changelog please? What is better about the new
algorithm?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-28 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 21:51 [PATCH 0/2] spi: fsl-dspi (vf610) clock fixes Aaron Brice
[not found] ` <1427493103-7354-1-git-send-email-aaron.brice-vSOi0k5x9wFWk0Htik3J/w@public.gmane.org>
2015-03-27 21:51 ` [PATCH 1/2] spi: fsl-dspi: Fix clock rate scale values Aaron Brice
2015-03-28 2:33 ` Mark Brown [this message]
2015-03-27 21:51 ` [PATCH 2/2] spi: fsl-dspi: Add ~50ns delay between cs and sck Aaron Brice
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=20150328023336.GL1743@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aaron.brice@datasoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=stefan@agner.ch \
/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).