All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] arm64: mvebu: Fix the bubt comamnd NAND device support
Date: Tue, 9 May 2017 16:41:52 +0200	[thread overview]
Message-ID: <77c9bb3a-c01d-4da1-feda-1eb39fa8686f@denx.de> (raw)
In-Reply-To: <1490714218-24012-4-git-send-email-kostap@marvell.com>

On 28.03.2017 17:16, kostap at marvell.com wrote:
> From: Konstantin Porotchkin <kostap@marvell.com>
>
> Fix the NAND structures in bubt command according to latest
> changes in MTD API.
>
> Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>
> Cc: Stefan Roese <sr@denx.de>
> Cc: Igal Liberman <igall@marvell.com>
> Cc: Nadav Haklai <nadavh@marvell.com>

Applied to u-boot-marvell/master.

Thanks,
Stefan

  parent reply	other threads:[~2017-05-09 14:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 15:16 [U-Boot] [PATCH 0/5] Add support for NAND flash to A7K/A8K SoC family kostap at marvell.com
2017-03-28 15:16 ` [U-Boot] [PATCH 1/5] fix: nand: pxa3xx: Remove hardcode values from the driver kostap at marvell.com
2017-05-08 12:28   ` Stefan Roese
2017-05-09 14:40   ` Stefan Roese
2017-03-28 15:16 ` [U-Boot] [PATCH 2/5] arm64: mvebu: a8k: Add support for NAND clock get kostap at marvell.com
2017-03-30 13:15   ` Stefan Roese
2017-03-30 15:46     ` Konstantin Porotchkin
2017-04-03  8:51       ` Stefan Roese
2017-03-28 15:16 ` [U-Boot] [PATCH 3/5] arm64: mvebu: Fix the bubt comamnd NAND device support kostap at marvell.com
2017-05-08 12:28   ` Stefan Roese
2017-05-09 14:41   ` Stefan Roese [this message]
2017-03-28 15:16 ` [U-Boot] [PATCH 4/5] arm64: a8k: dts: Add support for NAND devices on A8K platform kostap at marvell.com
2017-03-30 13:21   ` Stefan Roese
2017-03-28 15:16 ` [U-Boot] [PATCH 5/5] arm64: mvebu: a8k: Add NAND configuration parameters kostap at marvell.com
2017-04-19  8:44   ` Stefan Roese
2017-04-19  8:50     ` [U-Boot] [EXT] " Kostya Porotchkin
2017-04-19  8:55       ` Stefan Roese

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=77c9bb3a-c01d-4da1-feda-1eb39fa8686f@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.