linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Roland Stigge <stigge@antcom.de>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 0/3] mtd: nand: lpc32xx_slc: fix calculation of timing arcs from given values
Date: Sun, 4 Oct 2015 22:48:16 +0100	[thread overview]
Message-ID: <20151004214816.GB27301@localhost> (raw)
In-Reply-To: <1443655417-14689-1-git-send-email-vz@mleia.com>

On Thu, Oct 01, 2015 at 02:23:34AM +0300, Vladimir Zapolskiy wrote:
> The changeset is intended to accelerata read/write speed of LPC32xx SLC
> controller improving configuration of controller timing arcs.
> 
> Patch 2/3 is a defensive check against an unlikely case, when controller's
> clock rate is too high.
> 
> Thanks to Brian Norris for review and the idea of v2 3/3 improvement.
> 
> Vladimir Zapolskiy (3):
>   mtd: nand: lpc32xx_slc: improve SLCTAC_*() macro definitions
>   mtd: nand: lpc32xx_slc: fix potential overflow over 4 bits
>   mtd: nand: lpc32xx_slc: fix calculation of timing arcs from given values

All looks good to me. I won't hold my breath for Roland. Pushed to
l2-mtd.git, and if we get any further comments, we can address them
then.

Thanks,
Brian

      parent reply	other threads:[~2015-10-04 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 23:23 [PATCH v2 0/3] mtd: nand: lpc32xx_slc: fix calculation of timing arcs from given values Vladimir Zapolskiy
2015-09-30 23:23 ` [PATCH v2 1/3] mtd: nand: lpc32xx_slc: improve SLCTAC_*() macro definitions Vladimir Zapolskiy
2015-10-01  5:20   ` Vladimir Zapolskiy
2015-09-30 23:23 ` [PATCH v2 2/3] mtd: nand: lpc32xx_slc: fix potential overflow over 4 bits Vladimir Zapolskiy
2015-09-30 23:23 ` [PATCH v2 3/3] mtd: nand: lpc32xx_slc: fix calculation of timing arcs from given values Vladimir Zapolskiy
2015-10-04 21:48 ` Brian Norris [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=20151004214816.GB27301@localhost \
    --to=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=stigge@antcom.de \
    --cc=vz@mleia.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 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).