From: Rob Herring <robh@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
bbrezillon@kernel.org, richard@nod.at,
linux-kernel@vger.kernel.org, marek.vasut@gmail.com,
robh+dt@kernel.org, linux-mtd@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
computersforpeace@gmail.com, dwmw2@infradead.org
Subject: Re: [PATCH v2 2/2] dt-binding: mtd: physmap: Add example using addr-gpios property
Date: Sat, 06 Apr 2019 01:05:49 -0500 [thread overview]
Message-ID: <5ca841be.1c69fb81.9bbef.2ef4@mx.google.com> (raw)
In-Reply-To: <20190329021322.6833-3-chris.packham@alliedtelesis.co.nz>
On Fri, 29 Mar 2019 15:13:22 +1300, Chris Packham wrote:
> Add an example showing how to use the addr-gpios property to deal with a
> system with limited IO space.
>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> Changes in v2:
> - None
>
> .../devicetree/bindings/mtd/mtd-physmap.txt | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: bbrezillon@kernel.org, computersforpeace@gmail.com,
dwmw2@infradead.org, marek.vasut@gmail.com, richard@nod.at,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-binding: mtd: physmap: Add example using addr-gpios property
Date: Sat, 06 Apr 2019 01:05:49 -0500 [thread overview]
Message-ID: <5ca841be.1c69fb81.9bbef.2ef4@mx.google.com> (raw)
In-Reply-To: <20190329021322.6833-3-chris.packham@alliedtelesis.co.nz>
On Fri, 29 Mar 2019 15:13:22 +1300, Chris Packham wrote:
> Add an example showing how to use the addr-gpios property to deal with a
> system with limited IO space.
>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> Changes in v2:
> - None
>
> .../devicetree/bindings/mtd/mtd-physmap.txt | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: bbrezillon@kernel.org, computersforpeace@gmail.com,
dwmw2@infradead.org, marek.vasut@gmail.com, richard@nod.at,
robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH v2 2/2] dt-binding: mtd: physmap: Add example using addr-gpios property
Date: Sat, 06 Apr 2019 01:05:49 -0500 [thread overview]
Message-ID: <5ca841be.1c69fb81.9bbef.2ef4@mx.google.com> (raw)
In-Reply-To: <20190329021322.6833-3-chris.packham@alliedtelesis.co.nz>
On Fri, 29 Mar 2019 15:13:22 +1300, Chris Packham wrote:
> Add an example showing how to use the addr-gpios property to deal with a
> system with limited IO space.
>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> Changes in v2:
> - None
>
> .../devicetree/bindings/mtd/mtd-physmap.txt | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-04-06 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 2:13 [PATCH v2 0/2] mtd: physmap: Using gpio-addrs Chris Packham
2019-03-29 2:13 ` Chris Packham
2019-03-29 2:13 ` [PATCH v2 1/2] mtd: maps: physmap: Store gpio_values correctly Chris Packham
2019-03-29 2:13 ` Chris Packham
2019-03-29 2:13 ` [PATCH v2 2/2] dt-binding: mtd: physmap: Add example using addr-gpios property Chris Packham
2019-03-29 2:13 ` Chris Packham
2019-04-06 6:05 ` Rob Herring [this message]
2019-04-06 6:05 ` Rob Herring
2019-04-06 6:05 ` Rob Herring
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=5ca841be.1c69fb81.9bbef.2ef4@mx.google.com \
--to=robh@kernel.org \
--cc=bbrezillon@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=richard@nod.at \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.