From: Rob Herring <robh@kernel.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@arm.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/1] of: properties of reserved-memory nodes
Date: Tue, 15 Sep 2020 14:26:15 -0600 [thread overview]
Message-ID: <20200915202615.GA2450947@bogus> (raw)
In-Reply-To: <20200910162020.3927-1-xypron.glpk@gmx.de>
On Thu, 10 Sep 2020 18:20:20 +0200, Heinrich Schuchardt wrote:
> The reusable and the no-map property are mutually exclusive.
> Clarify this in the documentation.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> .../devicetree/bindings/reserved-memory/reserved-memory.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Applied, thanks!
prev parent reply other threads:[~2020-09-15 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 16:20 [PATCH 1/1] of: properties of reserved-memory nodes Heinrich Schuchardt
2020-09-10 16:49 ` Grant Likely
2020-09-15 20:26 ` Rob Herring [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=20200915202615.GA2450947@bogus \
--to=robh@kernel.org \
--cc=ardb@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=xypron.glpk@gmx.de \
/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).