From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] reworked fix for earlier ti81xx changes for v4.5 merge window
Date: Tue, 22 Dec 2015 17:44:45 -0800 [thread overview]
Message-ID: <pull-1450834180-928842> (raw)
Hi,
Here are reworked pull requests to separate the dts changes as requested
by Olof.
The pull request below, and the third pull request in this series,
still depend on the earlier branch omap-for-v4.5/81xx-fixes-signed.
The pull request number two in this series does not.
My updated for-next has zero diff with these merged in compared to the
earlier single branch merged in, so this is just regrouping of the patches
into three separate pull requests.
Regards,
Tony
The following changes since commit d893656e61040f3ff7b5f72a986052a348f3c94e:
ARM: OMAP2+: Remove useless check for legacy booting for dm814x (2015-12-09 16:53:46 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.5/81xx-fix-signed
for you to fetch changes up to dbb7e70a69288980c8a89fdb5ffb97e06b806b19:
ARM: OMAP2+: Fix randconfig build warning for dm814_pllss_data (2015-12-22 17:01:02 -0800)
----------------------------------------------------------------
Fix a randconfig build warning introduced in the earlier branch
omap-for-v4.5/81xx-fixes-signed.
----------------------------------------------------------------
Tony Lindgren (1):
ARM: OMAP2+: Fix randconfig build warning for dm814_pllss_data
arch/arm/mach-omap2/prm_common.c | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2015-12-23 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 1:44 Tony Lindgren [this message]
2015-12-23 1:44 ` [GIT PULL 2/3] reworked soc changes for ti81xx devices and minimal dra62x j5ec-evm support Tony Lindgren
2015-12-23 1:44 ` [GIT PULL 3/3] reworked dts " 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=pull-1450834180-928842 \
--to=tony@atomide.com \
--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).