From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: renesas-drivers-2015-01-08-v3.19-rc3
Date: Thu, 15 Jan 2015 11:11:37 +0000 [thread overview]
Message-ID: <CAMuHMdXwsEkeT3_wRVTKNE2jkzRmuph2zDNzqa4HeGy4gmm++w@mail.gmail.com> (raw)
In-Reply-To: <1420731718-12458-1-git-send-email-geert+renesas@glider.be>
Hi Simon,
On Thu, Jan 8, 2015 at 4:49 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Thu, Jan 8, 2015 at 4:41 PM, Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
>> I've pushed renesas-drivers-2015-01-08-v3.19-rc3 to
>> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
>
>> Included branches with driver code:
>> - clk-shmobile-for-3.20
>> - clk: shmobile: div6: Avoid changing divisor in .disable()
>> - clk: shmobile: Add r8a7793 support
>> - clk: shmobile: r8a7793: document CPG clock support
>> - clk: shmobile: r8a73a4 common clock framework implementation
>> - clk: shmobile: Add r8a73a4 SoC to MSTP bindings
>> - clk: shmobile: Add R-Car Gen2 RCAN clock support
>> - clk: shmobile: Add R-Car Gen2 ADSP clock support
>
> Given Mike hasn't acked all commits in the list above, and there are no urgent
> hard dependencies (all depending parts are DTS changes), I think it's best if I
> ask him (instead of you) to pull this.
>
> Note that he did ack the r8a73a4 CCF parts, so these can move forward at full
> speed.
>
> Do you agree?
Ping?
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
prev parent reply other threads:[~2015-01-15 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 15:41 renesas-drivers-2015-01-08-v3.19-rc3 Geert Uytterhoeven
2015-01-08 15:49 ` renesas-drivers-2015-01-08-v3.19-rc3 Geert Uytterhoeven
2015-01-15 11:11 ` Geert Uytterhoeven [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=CAMuHMdXwsEkeT3_wRVTKNE2jkzRmuph2zDNzqa4HeGy4gmm++w@mail.gmail.com \
--to=geert@linux-m68k.org \
--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).