From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Sh73a0 CCF Updates for v3.20
Date: Fri, 16 Jan 2015 11:45:50 +0900 [thread overview]
Message-ID: <cover.1421376276.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these second round of Renesas ARM based SoC sh73a0 CCF updates for v3.20.
This pull request is based on the previous round of
such requests, tagged as renesas-sh73a0-ccf-for-v3.20,
which you have already pulled.
The following changes since commit 09bd745b555c262d1e2c851777317f3adf3cf3d4:
ARM: shmobile: sh73a0: disable legacy clock initialization (2014-12-21 17:09:25 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh73a0-ccf2-for-v3.20
for you to fetch changes up to 16bd794f9432b556ec797cbf16c5e575a18f7030:
clk: shmobile: fix sparse NULL pointer warning (2015-01-14 13:13:24 +0900)
----------------------------------------------------------------
Second Round of Renesas ARM Based SoC Sh73a0 CCF Updates for v3.20
* Fix sparse NULL pointer warning
----------------------------------------------------------------
Wei Yongjun (1):
clk: shmobile: fix sparse NULL pointer warning
drivers/clk/shmobile/clk-sh73a0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2015-01-16 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 2:45 Simon Horman [this message]
2015-01-16 2:45 ` [PATCH] clk: shmobile: fix sparse NULL pointer warning Simon Horman
2015-01-21 23:14 ` [GIT PULL] Second Round of Renesas ARM Based SoC Sh73a0 CCF Updates for v3.20 Olof Johansson
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=cover.1421376276.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--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).