From: Doug Anderson <dianders@chromium.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Rob Herring <robh@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
<devicetree@vger.kernel.org>,
Andrey Pronin" <apronin@chromium.org>
Subject: Re: [PATCH] dt-bindings: tpm: Convert cr50 binding to YAML
Date: Tue, 7 Jan 2020 16:40:05 -0800 [thread overview]
Message-ID: <CAD=FV=UnYCSZy-OP3m2c4nKy4fw47z5qT6f7xzpQ-UJj5nO3DQ@mail.gmail.com> (raw)
In-Reply-To: <5e12cc29.1c69fb81.fe838.d5f3@mx.google.com>
Hi,
On Sun, Jan 5, 2020 at 9:57 PM Stephen Boyd <swboyd@chromium.org> wrote:
>
> > > I'd like to see if we can delete most of what you've written here.
> > > Specifically in "spi/spi-controller.yaml" you can see a really nice
> > > description of what SPI devices ought to look like. Can we just
> > > reference that? To do that I _think_ we actually need to break that
> > > description into a separate YAML file and then include it from there
> > > and here. Maybe someone on the list can confirm or we can just post
> > > some patches for that?
>
> I'm not sure what to do here.
Ignore me. I guess it's overkill to try to do this and I suppose if
someone ever wants to do it they can always do it later.
-Doug
next prev parent reply other threads:[~2020-01-08 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 0:54 [PATCH] dt-bindings: tpm: Convert cr50 binding to YAML Stephen Boyd
2019-12-17 17:45 ` Doug Anderson
2019-12-20 23:10 ` Rob Herring
[not found] ` <5e12cc29.1c69fb81.fe838.d5f3@mx.google.com>
2020-01-08 0:40 ` Doug Anderson [this message]
2020-01-16 17:58 ` Andrey Pronin
[not found] ` <5e174fec.1c69fb81.f3e14.8354@mx.google.com>
2020-02-01 1:35 ` Stephen Boyd
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='CAD=FV=UnYCSZy-OP3m2c4nKy4fw47z5qT6f7xzpQ-UJj5nO3DQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=apronin@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=swboyd@chromium.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).