From: Rob Herring <robh@kernel.org>
To: Jeffrey Kardatzke <jkardatzke@google.com>
Cc: Yi Chou <yich@chromium.org>,
devicetree-spec@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, Yi Chou <yich@google.com>,
Yi-An Chen <chenyian@google.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Simon Glass <sjg@chromium.org>,
etienne.carriere@linaro.org,
Julius Werner <jwerner@chromium.org>,
joakim.bech@linaro.org, etienne.carriere@foss.st.com
Subject: Re: [PATCH v2] schemas: Add Google Widevine initialization parameters
Date: Thu, 11 Jan 2024 14:16:58 -0600 [thread overview]
Message-ID: <CAL_JsqK2WHTGAUseTtOZKCCTT7Bz+tS1w1LGPRjpF_yh_shHuA@mail.gmail.com> (raw)
In-Reply-To: <CA+ddPcN-p=cCQUcDRt-33s0=EhZkBMPRFOqULbZS3YMfeP9=Fw@mail.gmail.com>
On Thu, Jan 11, 2024 at 12:31 PM Jeffrey Kardatzke
<jkardatzke@google.com> wrote:
>
> Can we get a review from maintainers now that we've posted this again?
To repeat what I asked for on v1, I'd like to see some acks from Optee
maintainers on this.
Instead I just got pointed to a GH discussion which AFAICT isn't
resolved. Specifically, Joakim raised the same point there as I did.
Rob
next prev parent reply other threads:[~2024-01-11 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 3:44 [PATCH v2] schemas: Add Google Widevine initialization parameters Yi Chou
2024-01-11 18:30 ` Jeffrey Kardatzke
2024-01-11 19:39 ` Krzysztof Kozlowski
2024-01-11 20:16 ` Rob Herring [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-13 7:48 Yi Chou
2024-01-08 17:40 ` Jeffrey Kardatzke
2024-01-08 18:53 ` Krzysztof Kozlowski
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=CAL_JsqK2WHTGAUseTtOZKCCTT7Bz+tS1w1LGPRjpF_yh_shHuA@mail.gmail.com \
--to=robh@kernel.org \
--cc=chenyian@google.com \
--cc=devicetree-spec@vger.kernel.org \
--cc=etienne.carriere@foss.st.com \
--cc=etienne.carriere@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=jkardatzke@google.com \
--cc=joakim.bech@linaro.org \
--cc=jwerner@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=sjg@chromium.org \
--cc=yich@chromium.org \
--cc=yich@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).