devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jeffrey Kardatzke <jkardatzke@google.com>, Yi Chou <yich@chromium.org>
Cc: devicetree-spec@vger.kernel.org, Rob Herring <robh@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 20:39:09 +0100	[thread overview]
Message-ID: <2151938c-8ab7-421c-a3b1-9175bae2a073@linaro.org> (raw)
In-Reply-To: <CA+ddPcN-p=cCQUcDRt-33s0=EhZkBMPRFOqULbZS3YMfeP9=Fw@mail.gmail.com>

On 11/01/2024 19:30, Jeffrey Kardatzke wrote:
> Can we get a review from maintainers now that we've posted this again?

I leave it for Rob. However your tone and impatience is not helping.
It's merge window. Please relax, and help out by reviewing other patches
on the mailing lists in order to relieve the burden of maintainers and
move your patches higher up the list.

Best regards,
Krzysztof


  reply	other threads:[~2024-01-11 19:39 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 [this message]
2024-01-11 20:16   ` Rob Herring
  -- 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=2151938c-8ab7-421c-a3b1-9175bae2a073@linaro.org \
    --to=krzysztof.kozlowski@linaro.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=robh@kernel.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).