From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-mtd@lists.infradead.org,
"Boris Brezillon" <bbrezillon@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-kernel@vger.kernel.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: mtd: move partition binding to its own file
Date: Mon, 25 Jan 2021 16:23:54 -0600 [thread overview]
Message-ID: <20210125222354.GA1131674@robh.at.kernel.org> (raw)
In-Reply-To: <20210115153901.31052-1-zajec5@gmail.com>
On Fri, 15 Jan 2021 16:38:59 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Single partition binding is quite common and may be:
> 1. Used by multiple parsers
> 2. Extended for more specific cases
>
> Move it to separated file to avoid code duplication.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../mtd/partitions/fixed-partitions.yaml | 33 +------------
> .../bindings/mtd/partitions/partition.yaml | 47 +++++++++++++++++++
> 2 files changed, 48 insertions(+), 32 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mtd/partitions/partition.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-01-25 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 15:38 [PATCH 1/3] dt-bindings: mtd: move partition binding to its own file Rafał Miłecki
2021-01-15 15:39 ` [PATCH 2/3] dt-bindings: mtd: add binding from BCM4908 partitions Rafał Miłecki
2021-01-25 22:42 ` Rob Herring
2021-01-15 15:39 ` [PATCH 3/3] mtd: parsers: ofpart: support BCM4908 fixed partitions Rafał Miłecki
2021-01-19 15:51 ` Miquel Raynal
2021-01-22 21:37 ` Richard Weinberger
2021-01-25 22:23 ` 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=20210125222354.GA1131674@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bbrezillon@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=zajec5@gmail.com \
/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).