public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Mark Brown <broonie@kernel.org>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	Rob Herring <robh+dt@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] regulator/mfd: dt-bindings: maxim,max77802: convert to dtschema
Date: Thu, 3 Mar 2022 09:47:45 +0000	[thread overview]
Message-ID: <YiCOwe4ykuvx/mRO@google.com> (raw)
In-Reply-To: <a401939d-ba65-4614-baa2-047914f55206@canonical.com>

On Wed, 02 Mar 2022, Krzysztof Kozlowski wrote:

> On 15/02/2022 08:53, Krzysztof Kozlowski wrote:
> > Hi,
> > 
> 
> Hi Lee,
> 
> This set also looks like it is clear to go.

Yes, they're all on-the-list.

I'll probably take them all into one branch and send out a PR.

Making 24 separate immutable branches is beyond my pay scale!

-- 
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2022-03-03  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  7:53 [PATCH v3 0/2] regulator/mfd: dt-bindings: maxim,max77802: convert to dtschema Krzysztof Kozlowski
2022-02-15  7:53 ` [PATCH v3 1/2] regulator: " Krzysztof Kozlowski
2022-03-07  9:43   ` Lee Jones
2022-02-15  7:53 ` [PATCH v3 2/2] dt-bindings: mfd: " Krzysztof Kozlowski
2022-03-07  9:43   ` Lee Jones
2022-03-02 19:15 ` [PATCH v3 0/2] regulator/mfd: dt-bindings: " Krzysztof Kozlowski
2022-03-03  9:47   ` Lee Jones [this message]
2022-03-07 13:00 ` Lee Jones
2022-03-07 13:01 ` [GIT PULL] Immutable branch between MFD, SPI and DT due for the v5.18 merge window Lee Jones

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=YiCOwe4ykuvx/mRO@google.com \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=javier@dowhile0.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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