All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: u-boot@lists.denx.de, Patrick Delaunay <patrick.delaunay@foss.st.com>
Subject: Re: [PATCH v2 1/5] doc: binding: scmi: link to latest Linux kernel binding
Date: Thu, 3 Mar 2022 14:16:34 -0500	[thread overview]
Message-ID: <20220303191634.GG5020@bill-the-cat> (raw)
In-Reply-To: <20220221082242.6349-1-etienne.carriere@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]

On Mon, Feb 21, 2022 at 09:22:38AM +0100, Etienne Carriere wrote:

> Changes SCMI bindings documentation to relate to Linux kernel
> source tree that recently changed the bindings description to YAML
> format.
> 
> Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>

Applied to u-boot/next, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2022-03-03 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21  8:22 [PATCH v2 1/5] doc: binding: scmi: link to latest Linux kernel binding Etienne Carriere
2022-02-21  8:22 ` [PATCH v2 2/5] sandbox: scmi: test against a single scmi agent Etienne Carriere
2022-03-03 19:16   ` Tom Rini
2022-02-21  8:22 ` [PATCH v2 3/5] scmi: change parameter dev in devm_scmi_process_msg Etienne Carriere
2022-03-03 19:16   ` Tom Rini
2022-02-21  8:22 ` [PATCH v2 4/5] firmware: scmi: fix sandbox and related tests for clock discovery Etienne Carriere
2022-03-03 19:16   ` Tom Rini
2022-02-21  8:22 ` [PATCH v2 5/5] clk: scmi: register scmi clocks with CCF Etienne Carriere
2022-02-25  6:33   ` Sean Anderson
2022-03-07 10:17     ` Etienne Carriere
2022-03-16 16:09       ` Sean Anderson
2022-03-03 19:16   ` Tom Rini
2022-03-03 19:16 ` Tom Rini [this message]

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=20220303191634.GG5020@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=etienne.carriere@linaro.org \
    --cc=patrick.delaunay@foss.st.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.