From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: dm816x: Correct NAND support nodes
Date: Mon, 26 Jun 2017 02:38:36 -0700 [thread overview]
Message-ID: <20170626093835.GU3730@atomide.com> (raw)
In-Reply-To: <1498045347-27324-1-git-send-email-trini@konsulko.com>
* Tom Rini <trini@konsulko.com> [170621 04:42]:
> The ELM node in dm816x.dtsi needs to declare the correct compatible
> value here as per the binding only one value is correct, and the current
> driver handles it correctly. We then add pinmux information for the
> NAND found on the EVM so that we do not rely on the ROM to do this for
> us, and also so that we do not try and probe NAND before we probe the
> ELM.
OK applying into omap-for-v4.13/dt as it's a fix. Only taking fixes
until -rc1 FYI all.
Regards,
Tony
prev parent reply other threads:[~2017-06-26 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 11:42 [PATCH 1/2] ARM: dts: dm816x: Correct NAND support nodes Tom Rini
2017-06-21 11:42 ` [PATCH 2/2] ARM: dts: dm816x: Correct the state of the write protect pin Tom Rini
2017-06-26 9:38 ` Tony Lindgren [this message]
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=20170626093835.GU3730@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).