From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Amlogic SoC updates for v4.8 (#2)
Date: Thu, 07 Jul 2016 17:54:43 +0200 [thread overview]
Message-ID: <7280262.xpcZxIb8HR@wuerfel> (raw)
In-Reply-To: <CAOi56cVG=WOMq+D8Cne_xGi7gkin1nPk9Xq5w3gyUVn68Oc3Vg@mail.gmail.com>
On Thursday, July 7, 2016 7:27:49 AM CEST Kevin Hilman wrote:
> On Thu, Jul 7, 2016 at 6:11 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Wednesday, July 6, 2016 3:48:24 PM CEST Kevin Hilman wrote:
> >> Amlogic SoC updates:
> >> - Kconfig updates for new GXBB clock driver
> >>
> >> ----------------------------------------------------------------
> >> Michael Turquette (2):
> >> arm: meson: explicitly select clk drivers
> >> arm64: amlogic: select gxbb clk driver
> >
> > Hmm, two patches that should go on two different branches...
> >
> > I know it's silly to send send two pull requests here, if you like
> > I'll just cherry-pick them into next/soc and next/arm64 instead.
>
> Yes please, thanks.
>
>
Ok, done.
Arnd
prev parent reply other threads:[~2016-07-07 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:48 [GIT PULL] Amlogic SoC updates for v4.8 (#2) Kevin Hilman
2016-07-07 13:11 ` Arnd Bergmann
2016-07-07 14:27 ` Kevin Hilman
2016-07-07 15:54 ` Arnd Bergmann [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=7280262.xpcZxIb8HR@wuerfel \
--to=arnd@arndb.de \
--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