linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner sunXi clock changes for 3.16
Date: Wed, 04 Jun 2014 08:12:16 -0700	[thread overview]
Message-ID: <20140604151216.10062.81810@quantum> (raw)
In-Reply-To: <20140604071922.GA5765@lukather>

Quoting Maxime Ripard (2014-06-04 00:19:22)
> Hi Mike,
> 
> On Tue, Jun 03, 2014 at 10:41:20AM -0700, Mike Turquette wrote:
> > Quoting Emilio L?pez (2014-06-01 12:13:48)
> > > Hi Mike,
> > > 
> > > Here is the sunxi clocks pull for 3.16. As you probably saw during the 
> > > cycle, this mostly contains improved A31 support and a bit of 
> > > housekeeping. Please note that this pull does *not* contain the MMC 
> > > clock patches Hans sent, as you merged those yourself on clk-next
> > 
> > Hi Emilio,
> > 
> > -rc8 is pretty late for me to take this in under normal circumstances,
> > and since the merge window opened early this time I will defer taking
> > this pull request in until 3.16-rc1 is released. It'll be one of the
> > first things applied to the new clk-next.
> 
> I know that Emilio has been pretty late at sending this, but at least
> the A31 USB clocks patches is quite important for us, since it would
> allow to add the A31 to Olof's boot test farm.

I guess you will still reap the benefits of Olof's boot testing if this
is merged after 3.16-rc1?

> 
> Could you reconsider merging this?
> 
> Just so that doesn't happen again, when do you expect the pull
> requests?

There isn't a hard rule for "must be in by -rcN". But I really don't
like taking patches after the merge window opens. Something bothers me
about the commitdate for patches in clk-next being later than the
commitdate for the new Linux major release. I always take some trivial
patches during this time, or fixes which are obvious and would have to
be sent for the next round of -rc's anyways, but features or new
hardware support is something I don't like to take after the merge
window opens.

I was bit a couple merge windows back by trying to be too aggressive
about sneaking stuff in at the last minute and I learned my lesson ;-)

Regards,
Mike

> 
> Thanks,
> Maxime
> 
> -- 
> Maxime Ripard, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com

  reply	other threads:[~2014-06-04 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 19:13 [GIT PULL] Allwinner sunXi clock changes for 3.16 Emilio López
2014-06-03 17:41 ` Mike Turquette
2014-06-04  7:19   ` Maxime Ripard
2014-06-04 15:12     ` Mike Turquette [this message]
2014-06-04 15:50       ` Maxime Ripard
2014-06-04 16:56         ` Mike Turquette

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=20140604151216.10062.81810@quantum \
    --to=mturquette@linaro.org \
    --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).