From: Simon Horman <horms+renesas@verge.net.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org,
Simon Horman <horms+renesas@verge.net.au>
Subject: [GIT PULL] SH Drivers Updates for v4.8
Date: Mon, 25 Jul 2016 02:29:37 +0000 [thread overview]
Message-ID: <cover.1469413328.git.horms+renesas@verge.net.au> (raw)
Hi Linus,
Please consider these SH drivers updates for v4.8.
I expect this to be my last pull request for these drivers as
it removes usage of them from Renesas ARM Based SoCs and my
co-maintenance of them.
The drivers are still used by some SH SoCs and listed under SUPERH
in the MAINTAINERS file.
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh-drivers-for-v4.8
for you to fetch changes up to 3fd0498b842f2932558797ec297dc30f6eb5cec0:
MAINTAINERS: Drop drivers/sh/ for Renesas ARM (2016-05-30 09:41:39 +0900)
----------------------------------------------------------------
SH Drivers Updates for v4.8
* Drop us of SH Drivers on Renesas ARM Based SoCs
----------------------------------------------------------------
Geert Uytterhoeven (2):
drivers: sh: Stop using the legacy clock domain on ARM
MAINTAINERS: Drop drivers/sh/ for Renesas ARM
MAINTAINERS | 1 -
drivers/Makefile | 1 -
drivers/sh/pm_runtime.c | 9 ---------
3 files changed, 11 deletions(-)
next reply other threads:[~2016-07-25 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 2:29 Simon Horman [this message]
2016-07-25 2:29 ` [PATCH 1/2] drivers: sh: Stop using the legacy clock domain on ARM Simon Horman
2016-07-25 2:29 ` [PATCH 2/2] MAINTAINERS: Drop drivers/sh/ for Renesas ARM Simon Horman
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.1469413328.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=ysato@users.sourceforge.jp \
/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).