From: Sven Van Asbroeck <thesven73@gmail.com>
To: TheSven73@googlemail.com, Shawn Guo <shawnguo@kernel.org>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org
Subject: [PATCH v4 0/3] bus: imx-weim
Date: Mon, 17 Dec 2018 10:47:57 -0500 [thread overview]
Message-ID: <20181217154800.7448-1-TheSven73@googlemail.com> (raw)
Support multiple address ranges per child node on imx-weim.
While we're at it, insert some code which guards against common config
conflicts.
v4:
pick up patch after one-week delay
Shawn Guo:
changed devicetree patch position in the set
clarified a confusing #define'd constant name
minor coding style fixes
v3:
added devicetree binding docs
v2:
corrected acme@... in commit message example
Sven Van Asbroeck (3):
dt-bindings: bus: imx-weim: document multiple address ranges per child
node
bus: imx-weim: support multiple address ranges per child node
bus: imx-weim: guard against timing configuration conflicts
.../devicetree/bindings/bus/imx-weim.txt | 32 ++++++++-
drivers/bus/imx-weim.c | 70 +++++++++++++++----
2 files changed, 86 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2018-12-17 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 15:47 Sven Van Asbroeck [this message]
2018-12-17 15:47 ` [PATCH v4 1/3] dt-bindings: bus: imx-weim: document multiple address ranges per child node Sven Van Asbroeck
2018-12-17 15:47 ` [PATCH v4 2/3] bus: imx-weim: support " Sven Van Asbroeck
2018-12-17 15:48 ` [PATCH v4 3/3] bus: imx-weim: guard against timing configuration conflicts Sven Van Asbroeck
2019-01-11 7:17 ` [PATCH v4 0/3] bus: imx-weim Shawn Guo
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=20181217154800.7448-1-TheSven73@googlemail.com \
--to=thesven73@gmail.com \
--cc=TheSven73@googlemail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.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).