From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes against v3.17-rc3
Date: Fri, 05 Sep 2014 08:10:34 -0700 [thread overview]
Message-ID: <7hiol2yufp.fsf@paris.lan> (raw)
In-Reply-To: <20140904230737.GA7319@atomide.com> (Tony Lindgren's message of "Thu, 4 Sep 2014 16:07:37 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
>
> Linux 3.17-rc3 (2014-08-31 18:23:04 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-fixes-against-v3.17-rc3
>
> for you to fetch changes up to c7cc9ba11f8c09a4d12af0fc4aa9f9b026cdd354:
>
> ARM: dts: dra7-evm: Add vtt regulator support (2014-09-04 12:49:22 -0700)
>
> ----------------------------------------------------------------
> Few fixes for omaps mostly for various devices to get them working
> properly on the new am437x and dra7 hardware for several devices
> such as I2C, NAND, DDR3 and USB. There's also a clock fix for omap3.
>
> And also included are two minor cosmetic fixes that are not
> stictly fixes for the new hardware support added recently to
> downgrade a GPMC warning into a debug statement, and fix the
> confusing comments for dra7-evm spi1 mux.
>
> Note that these are all .dts changes except for a GPMC change.
>
> ----------------------------------------------------------------
Applied to fixes,
Kevin
prev parent reply other threads:[~2014-09-05 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 23:07 [GIT PULL] omap fixes against v3.17-rc3 Tony Lindgren
2014-09-05 15:10 ` Kevin Hilman [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=7hiol2yufp.fsf@paris.lan \
--to=khilman@kernel.org \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).