From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/7] ARM: SoC changes for 4.7
Date: Thu, 19 May 2016 21:54:59 +0200 [thread overview]
Message-ID: <87eg8xj018.fsf@belgarion.home> (raw)
In-Reply-To: <8749147.ztcb6kVhye@wuerfel> (Arnd Bergmann's message of "Wed, 18 May 2016 00:07:24 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
.. zip ... removed Linux and lkml as this is pxa specific.
> Hi Linus,
>
> These are the first seven pull requests for arm-soc this time, there is
> one small follow-up coming once the dependencies for that have landed
> in your tree.
I was wondering if my pull requests will be part of this follow-up ?
I'm speaking of :
- https://patchwork.ozlabs.org/patch/617118/
- https://patchwork.ozlabs.org/patch/617119/
Even if from my persespective passing this cycle doesn't matter much, I don't
know if this matters to Stephen as CLK_IS_ROOT will remain one more cycle.
Cheers.
--
Robert
next prev parent reply other threads:[~2016-05-19 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 22:07 [GIT PULL 0/7] ARM: SoC changes for 4.7 Arnd Bergmann
2016-05-17 22:20 ` [GIT PULL 1/7] ARM: SoC cleanups and fixes for v4.7 Arnd Bergmann
2016-05-17 22:21 ` [GIT PULL 2/7] ARM: SoC platform updates " Arnd Bergmann
2016-05-17 22:21 ` [GIT PULL 3/7] ARM: SoC 64-bit changes " Arnd Bergmann
2016-05-17 22:23 ` [GIT PULL 4/7] ARM: DT updates " Arnd Bergmann
2016-05-17 22:24 ` [GIT PULL 5/7] ARM: 64-bit " Arnd Bergmann
2016-05-17 22:24 ` [GIT PULL 6/7] ARM: SoC defconfig " Arnd Bergmann
2016-05-17 22:26 ` [GIT PULL 7/7] ARM: SoC driver " Arnd Bergmann
2016-05-19 16:02 ` [GIT PULL 0/7] ARM: SoC changes for 4.7 Rob Herring
2016-05-20 12:04 ` Arnd Bergmann
2016-05-19 19:54 ` Robert Jarzmik [this message]
2016-05-20 19:01 ` Arnd Bergmann
2016-05-21 8:33 ` Robert Jarzmik
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=87eg8xj018.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--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).