linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>,
	Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
	Rob Herring <robh@kernel.org>, DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [GIT PULL] ARM: dt-bindings: aspeed for v5.20
Date: Thu, 21 Jul 2022 14:55:00 +0200	[thread overview]
Message-ID: <CAK8P3a1j=WUq8=VZz9aY5zkPeEMaF11w4PJF7evmY_JTsFoFZQ@mail.gmail.com> (raw)
In-Reply-To: <20220721072415.11424-1-krzysztof.kozlowski@linaro.org>

On Thu, Jul 21, 2022 at 9:24 AM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
> Hi Arnd and Olof,
>
> My two patches documenting existing Aspeed board compatibles were waiting for
> some time, so a month ago I decided to pick them up and include in the
> linux-next, so other developers - like David - can base their work on these.
> Unfortunately the responsibility for the patches was not cleared as I was
> waiting for some replies Joel and Andrew, so I also did not push them out to
> you. And then rc7 appeared and it is quite late now. That's my mistake, I
> should sort it out earlier.
>
> But anyway these were for a month in linux-next and other work [1] will need it.
>
> Can you grab them last minute? If not, could you queue it for v5.21?

Merged into arm/dt for 5.20 now.

      Arnd

  reply	other threads:[~2022-07-21 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21  7:24 [GIT PULL] ARM: dt-bindings: aspeed for v5.20 Krzysztof Kozlowski
2022-07-21 12:55 ` Arnd Bergmann [this message]
2022-07-22  2:12   ` Andrew Jeffery

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='CAK8P3a1j=WUq8=VZz9aY5zkPeEMaF11w4PJF7evmY_JTsFoFZQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=andrew@aj.id.au \
    --cc=arm@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=robh@kernel.org \
    --cc=soc@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;
as well as URLs for NNTP newsgroup(s).