From: Geert Uytterhoeven <geert+renesas@glider.be>
To: linux-sh@vger.kernel.org
Subject: renesas-drivers-2014-08-27-v3.17-rc2
Date: Wed, 27 Aug 2014 14:40:01 +0000 [thread overview]
Message-ID: <1409150401-26045-1-git-send-email-geert+renesas@glider.be> (raw)
I've pushed renesas-drivers-2014-08-27-v3.17-rc2 to
https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
This tree is meant to ease development of platform support and drivers for
Renesas ARM ("shmobile") SoCs. It's created by merging the for-next branches
of various subsystem trees into the development branch of Simon Horman's
renesas.git tree.
Today's version is based on renesas-devel-20140827v2-v3.17-rc2.
Included subsystem trees (the last 2 are new):
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git#linux-next
git://git.linaro.org/people/mturquette/linux.git#clk-next
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git#for-next
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git#for-next
git://git.infradead.org/users/dedekind/l2-mtd-2.6.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git#tty-next
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git#i2c for-next
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#for-next
git://gitorious.org/linux-can/linux-can-next.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git#usb-next
git://people.freedesktop.org/~airlied/linux#drm-next
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git#next
git://linuxtv.org/mchehab/media-next.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git#mmc-next
git://git.linaro.org/people/ulf.hansson/mmc.git#next
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git#for-next
git://git.linaro.org/people/daniel.lezcano/linux.git#clockevents next
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git#next
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/dmaengine.git#next
git://git.infradead.org/users/vkoul/slave-dma.git#next
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git#staging-next
git://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-arm.git#for-next
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git#next
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git#for-next
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2014-08-27 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1409150401-26045-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-sh@vger.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).