From: patchwork-bot+linux-amlogic@kernel.org
To: Alexander Stein <alexander.stein@mailbox.org>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH 1/1] spi: dt-bindings: amlogic, meson-gx-spicc: Fix schema for meson-g12a
Date: Tue, 07 Jul 2020 18:51:13 +0000 [thread overview]
Message-ID: <159414787310.3387.15626311492565257275.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200609165527.55183-1-alexander.stein@mailbox.org>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Tue, 9 Jun 2020 18:55:27 +0200 you wrote:
> This fixes the following warning during dtbs_check:
> ---
> spi@13000: clock-names: Additional items are not allowed ('pclk' was unexpected)
> spi@13000: clock-names: ['core', 'pclk'] is too long
> spi@13000: clocks: [[2, 23], [2, 258]] is too long
> spi@15000: clock-names: Additional items are not allowed ('pclk' was unexpected)
> spi@15000: clock-names: ['core', 'pclk'] is too long
> spi@15000: clocks: [[2, 29], [2, 261]] is too long
>
> [...]
Here is a summary with links:
- [1/1] spi: dt-bindings: amlogic, meson-gx-spicc: Fix schema for meson-g12a
https://git.kernel.org/khilman/linux-amlogic/c/a575357b6435c6dd988b8194c59eec83f6e5d5af
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-07-07 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:55 Alexander Stein
2020-06-10 10:05 ` Mark Brown
2020-06-10 11:04 ` Mark Brown
2020-07-07 18:51 ` patchwork-bot+linux-amlogic [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=159414787310.3387.15626311492565257275.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=alexander.stein@mailbox.org \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®