From: Christian Hewitt <christianshewitt@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org, "Kevin Hilman" <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
linux-amlogic@lists.infradead.org,
"Andreas Färber" <afaerber@suse.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 3/3] arm64: dts: meson: add support for the SmartLabs SML-5442TW
Date: Sun, 1 Mar 2020 08:16:20 +0400 [thread overview]
Message-ID: <7E2FA81A-9A24-433D-A674-C0C224FCB2DE@gmail.com> (raw)
In-Reply-To: <1jpndxgxqi.fsf@starbuckisacylon.baylibre.com>
> On 29 Feb 2020, at 8:32 pm, Jerome Brunet <jbrunet@baylibre.com> wrote:
[snip]
> The above does not compile against kevin's tree:
> 1# the audio dt device have not been added yet
> 2# the bindings deps of 3 different subsystem will be available in this
> tree with the next rc1
>
> I warned about this on IRC.
Sorry.. I saw notices on the mailing list that Mark Brown had applied
changes and assumed this meant that audio things would be available
for use. I’ll resubmit a v6 series without the audio nodes and wait for
the audio changes to percolate through.
Christian
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-03-01 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 12:25 [PATCH v5 0/3] arm64: dts: meson: add dts/bindings for " Christian Hewitt
2020-02-29 12:25 ` [PATCH v5 1/3] dt-bindings: add vendor prefix for SmartLabs LLC Christian Hewitt
2020-02-29 12:25 ` [PATCH v5 2/3] dt-bindings: arm: amlogic: add support for the SmartLabs SML-5442TW Christian Hewitt
2020-02-29 12:25 ` [PATCH v5 3/3] arm64: dts: meson: " Christian Hewitt
2020-02-29 16:32 ` Jerome Brunet
2020-03-01 4:16 ` Christian Hewitt [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=7E2FA81A-9A24-433D-A674-C0C224FCB2DE@gmail.com \
--to=christianshewitt@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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
all inboxes | Powered by JetHome®