From: Simon Horman <horms@verge.net.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
Kevin Hilman <khilman@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
Olof Johansson <olof@lixom.net>
Subject: Re: [GIT PULL] Renesas ARM Based SoC DT Fixes for v4.8
Date: Fri, 22 Jul 2016 10:59:24 +0900 [thread overview]
Message-ID: <20160722015924.GH21943@verge.net.au> (raw)
In-Reply-To: <7322553.kXvQYPfzzh@wuerfel>
On Thu, Jul 21, 2016 at 02:41:52PM +0200, Arnd Bergmann wrote:
> On Monday, July 18, 2016 11:39:35 AM CEST Simon Horman wrote:
> > Renesas ARM Based SoC DT Fixes for v4.8
> >
> > * Corrections to r8a7792
> >
>
> Merged into next/dt, thanks!
Thanks!
I have queued up another fix for v4.8 since sending the above to you.
This time it is an SoC (C-code) rather than a DT fix. I am wondering
if you could offer guidance on:
* If you would prefer me to split fixes out into separate (DT, SoC, ...)
branches? If so is that until around rc1 when everything has been
merged into the forthcoming release and thereafter you would prefer
a single fixes branch?
* What pace you would like me to send fixes. I guess it depends on
where we are in the cycle. Currently I put the changes in next and
send what I have about once a week (or not if there are none :).
Typically there are very few fixes. But as I already have 3 for v4.8,
including those in this pull request, I get the feeling a few more could
emerge before v4.8 is released.
next prev parent reply other threads:[~2016-07-22 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 2:39 [GIT PULL] Renesas ARM Based SoC DT Fixes for v4.8 Simon Horman
2016-07-18 2:39 ` [PATCH 1/2] ARM: dts: r8a7792: add PLL1 divided by 2 clock Simon Horman
2016-07-18 2:39 ` [PATCH 2/2] ARM: dts: r8a7792: remove ADSP clock Simon Horman
2016-07-21 12:41 ` [GIT PULL] Renesas ARM Based SoC DT Fixes for v4.8 Arnd Bergmann
2016-07-22 1:59 ` Simon Horman [this message]
2016-07-22 19:30 ` Arnd Bergmann
2016-07-25 2:15 ` Simon Horman
2016-07-25 4:30 ` Olof Johansson
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=20160722015924.GH21943@verge.net.au \
--to=horms@verge.net.au \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
/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).