From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: [ANNOUNCE] Renesas Tree is Closed for v3.14
Date: Mon, 30 Dec 2013 01:36:42 +0000 [thread overview]
Message-ID: <20131230013640.GA1944@verge.net.au> (raw)
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.
next reply other threads:[~2013-12-30 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 1:36 Simon Horman [this message]
2014-03-07 0:24 ` [ANNOUNCE] Renesas Tree is Closed for v3.15 Simon Horman
2014-03-07 8:56 ` Wolfram Sang
2014-03-07 9:01 ` Wolfram Sang
2014-03-11 2:27 ` Simon Horman
2014-05-15 5:22 ` [ANNOUNCE] Renesas Tree is Closed for v3.16 Simon Horman
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=20131230013640.GA1944@verge.net.au \
--to=horms@verge.net.au \
--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).