From: Rich Felker <dalias@libc.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sh@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v9 0/2] J-Core timer support
Date: Thu, 20 Oct 2016 14:29:13 -0400 [thread overview]
Message-ID: <20161020182913.GS19318@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.DEB.2.20.1610201955230.4938@nanos>
On Thu, Oct 20, 2016 at 07:56:09PM +0200, 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.
Thanks Thomas. Daniel, sorry if my above reply was harsh and thanks
again for all your help reviewing and getting this upstream.
Rich
prev parent reply other threads:[~2016-10-20 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 21:51 [PATCH v9 0/2] J-Core timer support Rich Felker
2016-10-13 21:51 ` [PATCH v9 1/2] of: add J-Core timer bindings Rich Felker
2016-10-13 21:51 ` [PATCH v9 2/2] clocksource: add J-Core timer/clocksource driver Rich Felker
2016-10-17 9:30 ` [PATCH v9 0/2] J-Core timer support Daniel Lezcano
2016-10-20 1:22 ` Rich Felker
2016-10-20 7:32 ` Daniel Lezcano
2016-10-20 15:15 ` Rich Felker
2016-10-20 17:56 ` Thomas Gleixner
2016-10-20 18:07 ` Thomas Gleixner
2016-10-20 18:18 ` Daniel Lezcano
2016-10-20 18:29 ` Rich Felker [this message]
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=20161020182913.GS19318@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).