[ANNOUNCE] Renesas Tree is Closed for v3.14

[ANNOUNCE] Renesas Tree is Closed for v3.14

[Simon Horman]

Hi,

The Renesas tree is now closed for v3.14.

I am not planning to accept any more patches for v3.14 other than fixes.
And I am not planning to send any more pull-request for v3.14 other than
fixes.

I have tagged renesas-next-v3.13-rc5-20131230-next-20131230 with the
branches that I have either already sent pull requests for or fixes that I
have queued up.

I do not plan to update this again until after v3.14-rc1 is released.


I have tagged renesas-devel-v3.13-rc5-20131230 which is based on
renesas-next-v3.13-rc5-20131230. It includes a small number of patches
queued up for v3.15.

I will continue queuing up patches for v3.15, including the
patches people have recently pinged me about queuing up.


I realise that there are patches that people anticipated would
make it into v3.14 but have not made the cut. I sympathise with this
but arm-soc has a cut-off of v3.13-rc6 and this means I have to have
things queued up well before then. Your understanding is appreciated.


Lastly, this week is a holiday in Japan and I am taking a holiday too.
I will try to check the list for urgent matters and I look forward
to working with you all in the new year.

[ANNOUNCE] Renesas Tree is Closed for v3.15

[Simon Horman]

Hi,

The Renesas tree is now closed for v3.15.

I am not planning to accept any more patches for v3.15 other than fixes.
And I am not planning to send any more pull-request for v3.15 other than
fixes.

I have tagged renesas-next-v3.14-rc1-20140306 with the
branches that I have either already sent pull requests for or fixes that I
have queued up.

I do not plan to update this again until after v3.15-rc1 is released.


I have tagged renesas-devel-v3.14-rc5-20140307 which is based on
renesas-next-v3.14-rc1-20140306 and v3.14-rc5. It includes a small number
of patches queued up for v3.16.

I will continue queuing up patches for v3.15 as they become ready.


I realise that there are most likely patches that people anticipated would
make it into v3.15 but have not made the cut. I sympathise with this
but arm-soc has a cut-off of v3.14-rc6 and this means I have to have
things queued up well before then. Your understanding is appreciated.

Re: [ANNOUNCE] Renesas Tree is Closed for v3.15

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 518 bytes --]


> The Renesas tree is now closed for v3.15.

Argh, I didn't see this coming :(

> I realise that there are most likely patches that people anticipated would
> make it into v3.15 but have not made the cut. I sympathise with this
> but arm-soc has a cut-off of v3.14-rc6 and this means I have to have
> things queued up well before then. Your understanding is appreciated.

I was about to post V3 of my r7s72100 CCF series today rebased to the
current devel tag (now that you applied its main dependency). Poor
thing!


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [ANNOUNCE] Renesas Tree is Closed for v3.15

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

> I was about to post V3 of my r7s72100 CCF series today rebased to the
> current devel tag (now that you applied its main dependency).

Never mind! Just found out that you applied the dependency ("Introduce
shmobile_clk_workaround()") to 3.16 anyhow :)


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [ANNOUNCE] Renesas Tree is Closed for v3.15

[Simon Horman]

On Fri, Mar 07, 2014 at 09:56:39AM +0100, Wolfram Sang wrote:
> 
> > The Renesas tree is now closed for v3.15.
> 
> Argh, I didn't see this coming :(
> 
> > I realise that there are most likely patches that people anticipated would
> > make it into v3.15 but have not made the cut. I sympathise with this
> > but arm-soc has a cut-off of v3.14-rc6 and this means I have to have
> > things queued up well before then. Your understanding is appreciated.
> 
> I was about to post V3 of my r7s72100 CCF series today rebased to the
> current devel tag (now that you applied its main dependency). Poor
> thing!

Time is always against us.

[ANNOUNCE] Renesas Tree is Closed for v3.16

[Simon Horman]

Hi,

The Renesas tree is now closed for arm-soc changes for v3.16.

I am not planning to accept any more patches for v3.16 other than fixes[1].
Fixes and branches needing fixes[1] aside, I am planning to send the last
set of pull-requests for v3.16 tomorrow.

I have tagged renesas-next-v3.15-rc1-20140515 which includes all patches I
have queued up. I have also tagged renesas-devel-v3.15-rc5-20140515. The
only difference between the two tags is that the former is based on
v3.15-rc1 while the latter is includes v3.15-rc5.

I now plan to start queuing up patches for v3.17, making them them
available in the devel branch. I will rebase them on top of v3.16-rc1 once
it is released and the result will become available in the next branch at
that time.

I realise that there may be patches that people anticipated would make it
into v3.16 but have not. I sympathise with this but arm-soc has a cut-off
of v3.15-rc6 and this means I have to have things queued up well before
then. I believe that in this release cycle I have cut things as fine as
possible and in future I hope to close the Renesas tree soon after the
release of v3.16-rc5. Your understanding is appreciated.

Lastly, I will be in Tokyo for Linux Con Japan next week.
I apologise if that results in any delays.


[1] At this time the only fix I am waiting on is one to either fix
    or remove genmai-reference support.
    https://patchwork.kernel.org/patch/4173801/
    This affects only the r7s72100-ccf-for-v3.16 branch.
    https://git.kernel.org/cgit/linux/kernel/git/horms/renesas.git/log/?h=r7s72100-ccf-for-v3.16