From mboxrd@z Thu Jan 1 00:00:00 1970 From: arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org (Arnaud Ebalard) Subject: Re: [PATCH 1/2] ARM: mvebu: Netgear RN104: Use Hardware BCH ECC Date: Sun, 07 Sep 2014 11:19:19 +0200 Message-ID: <87oaurg548.fsf@natisbad.org> References: <920c7e7169dc6aaaa3eb4bced2336d38e77b8864.1410035142.git.arno@natisbad.org> <20140907093851.377ddd29@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <20140907093851.377ddd29-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> (Thomas Petazzoni's message of "Sun, 7 Sep 2014 09:38:51 +0200") Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Thomas Petazzoni Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Ben Peddell , Jason Cooper , linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Ezequiel Garcia , Gregory Clement , Russell King , Brian Norris , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org Hi Thomas, Thomas Petazzoni writes: > 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. Yes. To be more explicit, if the patches are candidates for stable, I think they are only useful for 3.16.y (3.16 is the first kernel with 5b3e507820c6). As you point, backporting down to 3.14 would not hurt but would only be decorative. Cheers, a+ -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: arno@natisbad.org (Arnaud Ebalard) To: Thomas Petazzoni Subject: Re: [PATCH 1/2] ARM: mvebu: Netgear RN104: Use Hardware BCH ECC References: <920c7e7169dc6aaaa3eb4bced2336d38e77b8864.1410035142.git.arno@natisbad.org> <20140907093851.377ddd29@free-electrons.com> Date: Sun, 07 Sep 2014 11:19:19 +0200 In-Reply-To: <20140907093851.377ddd29@free-electrons.com> (Thomas Petazzoni's message of "Sun, 7 Sep 2014 09:38:51 +0200") Message-ID: <87oaurg548.fsf@natisbad.org> MIME-Version: 1.0 Content-Type: text/plain Cc: devicetree@vger.kernel.org, Ben Peddell , Jason Cooper , linux-mtd@lists.infradead.org, Ezequiel Garcia , Gregory Clement , Russell King , Brian Norris , linux-arm-kernel@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Thomas, Thomas Petazzoni writes: > 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. Yes. To be more explicit, if the patches are candidates for stable, I think they are only useful for 3.16.y (3.16 is the first kernel with 5b3e507820c6). As you point, backporting down to 3.14 would not hurt but would only be decorative. Cheers, a+ From mboxrd@z Thu Jan 1 00:00:00 1970 From: arno@natisbad.org (Arnaud Ebalard) Date: Sun, 07 Sep 2014 11:19:19 +0200 Subject: [PATCH 1/2] ARM: mvebu: Netgear RN104: Use Hardware BCH ECC In-Reply-To: <20140907093851.377ddd29@free-electrons.com> (Thomas Petazzoni's message of "Sun, 7 Sep 2014 09:38:51 +0200") References: <920c7e7169dc6aaaa3eb4bced2336d38e77b8864.1410035142.git.arno@natisbad.org> <20140907093851.377ddd29@free-electrons.com> Message-ID: <87oaurg548.fsf@natisbad.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Thomas, Thomas Petazzoni writes: > 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. Yes. To be more explicit, if the patches are candidates for stable, I think they are only useful for 3.16.y (3.16 is the first kernel with 5b3e507820c6). As you point, backporting down to 3.14 would not hurt but would only be decorative. Cheers, a+