From: "ivan.khoronzhuk" <ivan.khoronzhuk@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, grygorii.strashko@ti.com,
Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@kernel.crashing.org>,
Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Rob Landley <rob@landley.net>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 6/7] mtd: nand: davinci: extend description of bindings
Date: Wed, 20 Nov 2013 17:54:04 +0200 [thread overview]
Message-ID: <528CDB1C.1010806@ti.com> (raw)
In-Reply-To: <201311201646.21435.arnd@arndb.de>
On 11/20/2013 05:46 PM, Arnd Bergmann wrote:
> On Wednesday 20 November 2013, Ivan Khoronzhuk wrote:
>> Extend bindings for davinci_nand driver to be more clear.
>>
>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
>> ---
>> .../devicetree/bindings/mtd/davinci-nand.txt | 77 ++++++++++++++------
>> 1 file changed, 54 insertions(+), 23 deletions(-)
>
> Hi Ivan,
>
> The changes look good to me, but please clarify in the changeset description
> above whether this is a backwards-compatible change, a clarification without
> semantic changes, or an incompatible change (which should be avoided).
>
> Arnd
>
This is a clarification only, without semantic changes.
Thanks, I'll update.
--
Regards,
Ivan Khoronzhuk
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2013-11-20 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 15:22 [PATCH 0/7] Davinci nand driver fixes and updates Ivan Khoronzhuk
2013-11-20 15:22 ` [PATCH 1/7] mtd: nand: davinci: fix driver registration Ivan Khoronzhuk
2013-11-20 15:22 ` [PATCH 2/7] mtd: nand: davinci: return ENOMEM if memory allocation is failed Ivan Khoronzhuk
[not found] ` <1384960945-14528-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2013-11-20 15:22 ` [PATCH 3/7] mtd: nand: davinci: check required ti,davinci-chipselect property Ivan Khoronzhuk
2013-11-20 15:22 ` [PATCH 4/7] mtd: nand: davinci: simplify error handling Ivan Khoronzhuk
2013-11-20 20:13 ` [PATCH 0/7] Davinci nand driver fixes and updates Grygorii Strashko
2013-11-29 15:37 ` Santosh Shilimkar
2013-11-29 15:44 ` Grygorii Strashko
2013-11-20 15:22 ` [PATCH 5/7] mtd: nand: davinci: move bindings under mtd Ivan Khoronzhuk
2013-11-20 15:22 ` [PATCH 6/7] mtd: nand: davinci: extend description of bindings Ivan Khoronzhuk
[not found] ` <1384960945-14528-7-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2013-11-20 15:46 ` Arnd Bergmann
2013-11-20 15:54 ` ivan.khoronzhuk [this message]
2013-11-20 15:22 ` [PATCH 7/7] mtd: nand: davinci: adjust DT properties to MTD generic Ivan Khoronzhuk
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=528CDB1C.1010806@ti.com \
--to=ivan.khoronzhuk@ti.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=santosh.shilimkar@ti.com \
--cc=swarren@wwwdotorg.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).