From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
"Jarkko Nikula" <jarkko.nikula@bitmer.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/3] ARM: DTS: AM3517-EVM: Add support for UI board and Audio
Date: Mon, 24 Sep 2018 15:04:52 -0700 [thread overview]
Message-ID: <20180924220452.GH5662@atomide.com> (raw)
In-Reply-To: <20180923153718.15095-2-aford173@gmail.com>
* Adam Ford <aford173@gmail.com> [180923 15:41]:
> The full AM3517-EVM shipped with an add-on board which contained
> two Audio codecs, a GPIO expander with a variety of buttons, and
> some other features. This patch enables these portions of the UI
> board because they don't directly conflict with existing features.
Applying this one into omap-for-v4.20/dt thanks.
Tony
next prev parent reply other threads:[~2018-09-24 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 15:37 [PATCH 1/3] ARM: configs: omap2plus: Add tlv320aic23 as module Adam Ford
2018-09-23 15:37 ` [PATCH 2/3] ARM: DTS: AM3517-EVM: Add support for UI board and Audio Adam Ford
2018-09-24 22:04 ` Tony Lindgren [this message]
2018-09-23 15:37 ` [PATCH 3/3] ARM: OMAP2PLUS: Remove references to AM3517-EVM since it's in DT Adam Ford
2018-09-23 16:23 ` Jarkko Nikula
2018-09-24 22:06 ` Tony Lindgren
2018-09-24 22:22 ` [PATCH 1/3] ARM: configs: omap2plus: Add tlv320aic23 as module Tony Lindgren
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=20180924220452.GH5662@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@bitmer.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
/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).