Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [ANNOUNCE] Renesas tree closed for v4.7
Date: Wed, 27 Apr 2016 10:54:11 +1000	[thread overview]
Message-ID: <20160427005410.GE18566@verge.net.au> (raw)
In-Reply-To: <20160427005222.GD18566@verge.net.au>

On Wed, Apr 27, 2016 at 10:52:22AM +1000, Simon Horman wrote:
> Hi,
> 
> I would like to stop accepting non-bug-fix patches for v4.6 and get
> the last pull requests posted by the end of this week.  This is in order
> for them to be sent before the release of v4.5-rc6, the deadline set by the

The version mentioned above should be v4.6-rc6.

> ARM SoC maintainers.  As patches should ideally progress from the renesas
> tree into linux-next before sending pull requests there is a few days lead
> time involved.
> 
> I intend to begin queueing up patches for v4.7 in the near future. 

  reply	other threads:[~2016-04-27  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  0:52 [ANNOUNCE] Renesas tree closed for v4.7 Simon Horman
2016-04-27  0:54 ` Simon Horman [this message]
2016-04-27 10:51   ` Sergei Shtylyov
2016-04-27 22:53     ` 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=20160427005410.GE18566@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-renesas-soc@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