linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] mtd: nand: gpmi: add i.MX 7 support
Date: Fri, 21 Apr 2017 04:33:04 +0200	[thread overview]
Message-ID: <644017ff-7b26-143c-df2f-1223841c81f4@gmail.com> (raw)
In-Reply-To: <20170421010755.18025-1-stefan@agner.ch>

On 04/21/2017 03:07 AM, Stefan Agner wrote:
> This patchset adds support for i.MX 7 SoC for the GPMI NAND controller.
> There have been similar patchsets already:
> https://lkml.org/lkml/2016/2/23/912
> 
> However, this patchset does not make use of any of the new features.
> The current feature set seems to work fine, I successfully run the MTD
> tests on a Colibri iMX7.
> 
> --

The rest of the patchset is IMO OK too, but you probably want the DT
changes Acked by Shawn or Fabio.

-- 
Best regards,
Marek Vasut

      parent reply	other threads:[~2017-04-21  2:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  1:07 [PATCH 0/5] mtd: nand: gpmi: add i.MX 7 support Stefan Agner
2017-04-21  1:07 ` [PATCH 1/5] mtd: nand: gpmi: unify clock handling Stefan Agner
2017-04-21  2:02   ` Marek Vasut
2017-04-21  1:07 ` [PATCH 2/5] mtd: nand: gpmi: add i.MX 7 SoC support Stefan Agner
2017-04-21  2:03   ` Marek Vasut
2017-04-21  3:15     ` Stefan Agner
2017-04-21 13:08       ` Marek Vasut
2017-04-21 16:19         ` Stefan Agner
2017-04-21 17:22           ` Marek Vasut
2017-04-21 17:38             ` Stefan Agner
2017-04-21 18:29               ` Han Xu
2017-05-02  9:17                 ` Boris Brezillon
2017-05-02 11:18                   ` Marek Vasut
2017-05-03 21:24                     ` Stefan Agner
2017-04-21  1:07 ` [PATCH 3/5] mtd: gpmi: document current clock requirements Stefan Agner
2017-04-21  1:07 ` [PATCH 4/5] ARM: dts: imx7: add GPMI NAND Stefan Agner
2017-04-21  1:07 ` [PATCH 5/5] ARM: dts: imx7-colibri: add NAND support Stefan Agner
2017-04-21  2:33 ` Marek Vasut [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=644017ff-7b26-143c-df2f-1223841c81f4@gmail.com \
    --to=marek.vasut@gmail.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).