devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
	tony@atomide.com, "Miquèl Raynal" <miquel.raynal@bootlin.com>
Cc: robh+dt@kernel.org, grygorii.strashko@ti.com, nm@ti.com,
	lokeshvutla@ti.com, nsekhar@ti.com, miquel.raynal@bootlin.com,
	devicetree@vger.kernel.org, linux-mtd@lists.infradead.org,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/8] dt-bindings: memory-controllers: ti,gpmc: Convert to yaml
Date: Fri, 8 Oct 2021 22:10:15 +0300	[thread overview]
Message-ID: <e165b6ee-91d3-3a50-3b9d-3f15fa82a101@kernel.org> (raw)
In-Reply-To: <6b90a6fd-001f-a41a-b69f-2bd3ec8a8e26@canonical.com>

Krzysztof,

On 07/10/2021 20:37, Krzysztof Kozlowski wrote:
> On 07/10/2021 14:08, Roger Quadros wrote:
>> Hi,
>>
>> This series converts ti,gpmc memory controller and ti,gpmc-nand and
>> ti,gpmc-onenand MTD controller bindings to yaml.
>>
>> cheers,
>> -roger
>>
> 
> Hi,
> 
> Although you did not mention it here, it looks like you have some
> dependencies between the patches. Maybe this shall go simply via Rob's tree?
> 

Rob has acked all the DT binding patches.
So it is upto you and Miquèl to decide the best way. MTD tree or Memory controller tree
for the dt-bindings patches.

The ARM: dts changes should go via Tony's OMAP SoC tree.

Or if Tony is OK with it then maybe all patches can go via Tony's tree? :)

cheers,
-roger


  reply	other threads:[~2021-10-08 19:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 12:08 [PATCH v5 0/8] dt-bindings: memory-controllers: ti,gpmc: Convert to yaml Roger Quadros
2021-10-07 12:08 ` [PATCH v5 1/8] dt-bindings: mtd: Remove gpmc-nor.txt Roger Quadros
2021-10-07 12:08 ` [PATCH v5 2/8] dt-bindings: net: Remove gpmc-eth.txt Roger Quadros
2021-10-07 12:08 ` [PATCH v5 3/8] dt-bindings: memory-controllers: Introduce ti,gpmc-child Roger Quadros
2021-10-09 14:52   ` Krzysztof Kozlowski
2021-10-07 12:08 ` [PATCH v5 4/8] dt-bindings: mtd: ti,gpmc-nand: Convert to yaml Roger Quadros
2021-10-07 12:08 ` [PATCH v5 5/8] dt-bindings: mtd: ti,gpmc-onenand: " Roger Quadros
2021-10-07 12:08 ` [PATCH v5 6/8] dt-bindings: memory-controllers: ti,gpmc: " Roger Quadros
2021-10-09 14:54   ` Krzysztof Kozlowski
2021-10-07 12:08 ` [PATCH v5 7/8] ARM: dts: omap: Fix boolean properties gpmc,cycle2cycle-{same|diff}csen Roger Quadros
2021-10-07 12:08 ` [PATCH v5 8/8] ARM: dts: omap: fix gpmc,mux-add-data type Roger Quadros
2021-10-07 17:37 ` [PATCH v5 0/8] dt-bindings: memory-controllers: ti,gpmc: Convert to yaml Krzysztof Kozlowski
2021-10-08 19:10   ` Roger Quadros [this message]
2021-10-09 14:55     ` Krzysztof Kozlowski
2021-10-11  5:53       ` Tony Lindgren
2021-10-11  7:03         ` Roger Quadros
2021-10-11 10:31           ` Tony Lindgren

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=e165b6ee-91d3-3a50-3b9d-3f15fa82a101@kernel.org \
    --to=rogerq@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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).