From: Tony Lindgren <tony@atomide.com>
To: Rob Herring <robh@kernel.org>
Cc: "Colin Foster" <colin.foster@in-advantage.com>,
"Andrew Davis" <afd@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
soc@kernel.org, "Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board
Date: Mon, 27 Feb 2023 09:15:07 +0200 [thread overview]
Message-ID: <Y/xYe9IOsXWBxtxK@atomide.com> (raw)
In-Reply-To: <20230226172248.GA47940-robh@kernel.org>
* Rob Herring <robh@kernel.org> [230226 17:22]:
> On Thu, Feb 23, 2023 at 08:25:08AM -0800, Colin Foster wrote:
> > On Thu, Feb 23, 2023 at 10:00:50AM -0600, Andrew Davis wrote:
> > > On 2/22/23 2:38 PM, Colin Foster wrote:
> > > > Add yaml documentation for TI OMAP devices for the Phytec PCM-049 SoM and
> > > > the Phytec PCM-959 development kit.
> > > >
> > > > Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> > > > ---
> > > >
> > > > v4
> > > > * New patch, based on a WIP from Andrew Davis <afd@ti.com>
> > > >
> > > > ---
> > > > .../devicetree/bindings/arm/ti,omap.yaml | 29 +++++++++++++++++++
> > > > 1 file changed, 29 insertions(+)
> > > > create mode 100644 Documentation/devicetree/bindings/arm/ti,omap.yaml
> > >
> > > How will this work if I add the same file? Why not take my WIP patch, make
> > > the suggested changes from Rob, then have it as your first patch in this
> > > series?
> >
> > Is your WIP intended to convert all omap.txt to ti,omap.yaml? Or chunk
> > off devices one at a time?
> >
> > If the former, when your patch is done it should be a pretty simple
> > rebase conflict resolution. If the latter (which feels more digestable)
> > this offers that template. This was Rob's / Tony's suggestion, albeit
> > before you sent your patch set.
> >
> >
> > Anyway, I'm happy to do any of the following:
> >
> > 1. Take Andrew's patches, add these references and re-submit.
> > 2. Keep this set as-is (with the typo fix) and when Andrew's WIP is done
> > it should be an easy rebase before submission.
> > 3. Wait for Andrew's WIP to be done, then submit with this update.
> >
> >
> > I'd like to avoid #3 because I don't know where this might fall on your
> > priorities list.
>
> If you are willing to do #1, that's certainly my preference.
That would be great!
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-27 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 20:38 [PATCH v4 0/2] add support for Phytec PCM-049 and PCM-959 Colin Foster
2023-02-22 20:38 ` [PATCH v4 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board Colin Foster
2023-02-22 21:40 ` Colin Foster
2023-02-23 16:00 ` Andrew Davis
2023-02-23 16:25 ` Colin Foster
2023-02-23 17:17 ` Andrew Davis
2023-02-26 17:22 ` Rob Herring
2023-02-27 7:15 ` Tony Lindgren [this message]
2023-02-22 20:38 ` [PATCH v4 2/2] arm: dts: omap4: pcm959: add initial support for phytec pcm959 Colin Foster
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=Y/xYe9IOsXWBxtxK@atomide.com \
--to=tony@atomide.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=colin.foster@in-advantage.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=soc@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).