From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Arnaud Ebalard <arno@natisbad.org>
Cc: devicetree@vger.kernel.org,
Ben Peddell <klightspeed@killerwolves.net>,
Jason Cooper <jason@lakedaemon.net>,
linux-mtd@lists.infradead.org,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Russell King <linux@arm.linux.org.uk>,
Brian Norris <computersforpeace@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: mvebu: Netgear RN104: Use Hardware BCH ECC
Date: Sun, 7 Sep 2014 09:38:51 +0200 [thread overview]
Message-ID: <20140907093851.377ddd29@free-electrons.com> (raw)
In-Reply-To: <920c7e7169dc6aaaa3eb4bced2336d38e77b8864.1410035142.git.arno@natisbad.org>
Dear Arnaud Ebalard,
On Sat, 06 Sep 2014 22:49:25 +0200, Arnaud Ebalard wrote:
> Fixes: 0373a558bd79 ("ARM: mvebu: Enable NAND controller in ReadyNAS 104 .dts file")
> Depends-on: 5b3e507820c6 ("mtd: nand: pxa3xx: Use ECC strength and step size devicetree binding")
Maybe it's worth noting that it's not a build dependency: your commit
changing the Device Tree files can perfectly be applied without the
NAND ECC strength and step size bindings. Of course, it will have no
effect on an older kernel that doesn't support those bindings, but it
will not cause a build failure.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-07 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 20:48 [PATCH 0/2] ARM: mvebu: Use Hardware BCH ECC for RN104 and RN2120 Arnaud Ebalard
2014-09-06 20:49 ` [PATCH 1/2] ARM: mvebu: Netgear RN104: Use Hardware BCH ECC Arnaud Ebalard
2014-09-07 7:38 ` Thomas Petazzoni [this message]
2014-09-07 9:19 ` Arnaud Ebalard
2014-09-06 20:49 ` [PATCH 2/2] ARM: mvebu: Netgear RN2120: " Arnaud Ebalard
2014-09-09 15:53 ` [PATCH 0/2] ARM: mvebu: Use Hardware BCH ECC for RN104 and RN2120 Jason Cooper
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=20140907093851.377ddd29@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=arno@natisbad.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=klightspeed@killerwolves.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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