[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191220113155.28177-1-yamada.masahiro@socionext.com>
Date: Fri, 20 Dec 2019 20:31:50 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: linux-mtd@...ts.infradead.org
Cc: Dinh Nguyen <dinguyen@...nel.org>, Marek Vasut <marex@...x.de>,
Ley Foon Tan <ley.foon.tan@...el.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Mark Rutland <mark.rutland@....com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Richard Weinberger <richard@....at>,
Rob Herring <robh+dt@...nel.org>,
Vignesh Raghavendra <vigneshr@...com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/5] mtd: rawnand: denali: a bungle of denali patches that is cleanly applicable
Some Denali driver patches are flying in ML.
The recently re-submitted patch
http://patchwork.ozlabs.org/patch/1213986/
... caused a conflict with:
http://patchwork.ozlabs.org/patch/1205912/
Instead of discussing "who should rebase his patch" again,
I offer to rebase and tidy up all the patches in a series
(if useful for the NAND maintainer).
Marek Vasut (1):
mtd: rawnand: denali_dt: Add support for configuring
SPARE_AREA_SKIP_BYTES
Masahiro Yamada (4):
mtd: rawnand: denali_dt: error out if platform has no associated data
dt-bindings: mtd: denali_dt: document reset property
mtd: rawnand: denali_dt: add reset controlling
mtd: rawnand: denali: remove hard-coded DENALI_DEFAULT_OOB_SKIP_BYTES
.../devicetree/bindings/mtd/denali-nand.txt | 7 +++
drivers/mtd/nand/raw/denali.c | 14 ++---
drivers/mtd/nand/raw/denali_dt.c | 56 +++++++++++++++++--
3 files changed, 64 insertions(+), 13 deletions(-)
--
2.17.1
Powered by blists - more mailing lists