From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH v9 0/2] J-Core timer support References: <20161017093013.GA1703@mai> <20161020012225.GK19318@brightrain.aerifal.cx> <20161020073240.GF1703@mai> <20161020151552.GQ19318@brightrain.aerifal.cx> From: Daniel Lezcano Message-ID: Date: Thu, 20 Oct 2016 20:18:11 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: Thomas Gleixner , Rich Felker Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org, Rob Herring , Mark Rutland List-ID: On 20/10/2016 20:07, Thomas Gleixner wrote: > On Thu, 20 Oct 2016, Thomas Gleixner wrote: >> Daniel, >> >> On Thu, 20 Oct 2016, Rich Felker wrote: >>> On Thu, Oct 20, 2016 at 09:32:40AM +0200, Daniel Lezcano wrote: >>>> Unfortunately it won't happen. v4.9-rc1 is already out. The driver will be >>>> in v4.10. >>>> >>>> If you wanted patches merged for v4.9, they should have been merged in the >>>> downstream tree before v4.8-rc5, so they hit the upstream tree for v4.9's merge >>>> window. >>> >>> I've been trying to get what's essentially the same patch merged since >>> before the 4.8 merge window. I would be more understanding if this >>> were something new that's not upstream, but broken support for the >>> hardware (that, from a user perspective, is a bug, since they can >>> select the target but then it doesn't boot) has already been in one >>> release due to missing core drivers, and the irq patches have already >>> been merged in this release (post-rc1 even). >> >> It's hardware enablement and not a new feature, so it's fine to merge it >> now. I'll pick it up later tonight. > > Daniel, it's the top two commits in your 4.10 branch. So it's not a big > deal to zap them. Yes, sure. No problem. Thanks! -- Daniel -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog