From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"gnurou@gmail.com" <gnurou@gmail.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH 0/6] apalis-tk1: updates for v1.1 hw
Date: Tue, 3 Jan 2017 13:20:48 +0000 [thread overview]
Message-ID: <1483449646.2745.1.camel@toradex.com> (raw)
In-Reply-To: <20161124010456.24604-1-marcel@ziswiler.com>
On Thu, 2016-11-24 at 02:04 +0100, marcel@ziswiler.com wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
>
> This series updates the device tree for the upcoming V1.1 HW samples.
> All changes are purely opportunistic meaning they fix stuff which on
> older HW was anyway broken so there should be no backwards
> compatibility issues.
>
>
> Marcel Ziswiler (6):
> apalis-tk1: remove spurious new lines
> apalis-tk1: temp alert pull-up
> apalis-tk1: optional displayport hot-plug detect
> apalis-tk1: adjust pin muxing for v1.1 hw
> apalis-tk1: working sd card detect on v1.1 hw
> apalis-tk1: update compatibility comment
>
> arch/arm/boot/dts/tegra124-apalis-eval.dts | 11 +----
> arch/arm/boot/dts/tegra124-apalis.dtsi | 73 +++++++++++---------
> ----------
> 2 files changed, 29 insertions(+), 55 deletions(-)
Ping.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-01-03 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 1:04 [RESEND PATCH 0/6] apalis-tk1: updates for v1.1 hw marcel
2016-11-24 1:04 ` [RESEND PATCH 1/6] apalis-tk1: remove spurious new lines marcel
2016-11-24 1:04 ` [RESEND PATCH 2/6] apalis-tk1: temp alert pull-up marcel
[not found] ` <20161124010456.24604-1-marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>
2016-11-24 1:04 ` [RESEND PATCH 3/6] apalis-tk1: optional displayport hot-plug detect marcel-mitwqZ+T+m9Wk0Htik3J/w
2016-11-24 1:04 ` [RESEND PATCH 4/6] apalis-tk1: adjust pin muxing for v1.1 hw marcel
2016-11-24 1:04 ` [RESEND PATCH 5/6] apalis-tk1: working sd card detect on " marcel
2016-11-24 1:04 ` [RESEND PATCH 6/6] apalis-tk1: update compatibility comment marcel
2017-01-03 13:20 ` Marcel Ziswiler [this message]
[not found] ` <1483449646.2745.1.camel-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
2017-01-25 6:56 ` [RESEND PATCH 0/6] apalis-tk1: updates for v1.1 hw Thierry Reding
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=1483449646.2745.1.camel@toradex.com \
--to=marcel.ziswiler@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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).