From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org
Subject: Re: [PATCH v3 0/3] ARM: dts: omap5 uevm: add LEDs, USR1 button and EEPROM
Date: Wed, 9 Nov 2016 15:03:26 -0700 [thread overview]
Message-ID: <20161109220325.GG2428@atomide.com> (raw)
In-Reply-To: <cover.1475126737.git.hns@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [160928 22:26]:
> Changes V3:
> * remove unit addresses from LEDs [Rob Herring]
>
> 2016-09-28 20:08:23: Changes V2:
> * fixed subject of patches to correctly tell that it is for omap5 evm
> * changed default triggers a little to create a nicer default pattern
>
> 2016-09-27 07:26:14: These patches configure
> * the EEPROM
> * the LEDs (with some default triggers)
> * the USR1 gpio button
> for the OMAP5 UEVM board.
>
> H. Nikolaus Schaller (3):
> ARM: dts: omap5 uevm: add EEPROM
> ARM: dts: omap5 uevm: add LEDs
> ARM: dts: omap5 uevm: add USR1 button
Applying all into omap-for-v4.10/dt thanks.
Tony
prev parent reply other threads:[~2016-11-09 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 5:25 [PATCH v3 0/3] ARM: dts: omap5 uevm: add LEDs, USR1 button and EEPROM H. Nikolaus Schaller
[not found] ` <cover.1475126737.git.hns-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
2016-09-29 5:25 ` [PATCH v3 1/3] ARM: dts: omap5 uevm: add EEPROM H. Nikolaus Schaller
2016-09-29 5:25 ` [PATCH v3 2/3] ARM: dts: omap5 uevm: add LEDs H. Nikolaus Schaller
2016-09-29 5:25 ` [PATCH v3 3/3] ARM: dts: omap5 uevm: add USR1 button H. Nikolaus Schaller
2016-11-09 22:03 ` Tony Lindgren [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=20161109220325.GG2428@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).