From: Jonathan Cameron <jic23@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: "William Breathitt Gray" <vilhelm.gray@gmail.com>,
"David Lechner" <david@lechnology.com>,
linux-iio@vger.kernel.org, linux-omap@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v3 0/6] counter: new TI eQEP driver
Date: Sun, 8 Sep 2019 12:16:18 +0100 [thread overview]
Message-ID: <20190908121618.3e7e5618@archlinux> (raw)
In-Reply-To: <20190905141053.GU52127@atomide.com>
On Thu, 5 Sep 2019 07:10:53 -0700
Tony Lindgren <tony@atomide.com> wrote:
> * William Breathitt Gray <vilhelm.gray@gmail.com> [190905 13:38]:
> > On Sun, Sep 01, 2019 at 05:58:21PM -0500, David Lechner wrote:
> > > This series adds device tree bindings and a new counter driver for the Texas
> > > Instruments Enhanced Quadrature Encoder Pulse (eQEP).
> > >
> > > As mentioned in one of the commit messages, to start with, the driver only
> > > supports reading the current counter value and setting the min/max values.
> > > Other features can be added as the counter subsystem gains support for them.
> ...
>
> > I'm satisfied with this version of the patchset.
> >
> > Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> >
> > Jonathan, if you have no objections please pick up this up so that it
> > can make it to the 5.4 merge window coming in soon. Alternatively, I can
> > merge it into my repository instead and hold it for a while longer
> > there, if you prefer that route.
>
> Looks good to me too:
>
> Acked-by: Tony Lindgren <tony@atomide.com>
Sorry, too close to the likely opening of the 5.4 merge window for it to
go via IIO this cycle (unless there is a significant delay for some reason!)
I'm happy to queue it up for 5.5 but before I do this, see replies to patch 1
about whether an immutable branch is needed as we are going across multiple
trees.
Thanks,
Jonathan
prev parent reply other threads:[~2019-09-08 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 22:58 [PATCH v3 0/6] counter: new TI eQEP driver David Lechner
2019-09-01 22:58 ` [PATCH v3 1/6] bus/ti-pwmss: move TI PWMSS driver from PWM to bus subsystem David Lechner
2019-09-02 15:02 ` Thierry Reding
2019-09-08 11:15 ` Jonathan Cameron
2019-09-08 19:44 ` Tony Lindgren
2019-10-17 20:58 ` Jonathan Cameron
2019-09-01 22:58 ` [PATCH v3 2/6] dt-bindings: counter: new bindings for TI eQEP David Lechner
2019-09-02 15:02 ` Rob Herring
2019-09-01 22:58 ` [PATCH v3 3/6] counter: new TI eQEP driver David Lechner
2019-09-01 22:58 ` [PATCH v3 4/6] ARM: dts: am33xx: Add nodes for eQEP David Lechner
2019-09-01 22:58 ` [PATCH v3 5/6] ARM: dts: am335x-boneblue: Enable eQEP David Lechner
2019-09-02 14:17 ` [PATCH v3 0/6] counter: new TI eQEP driver David Lechner
2019-09-05 13:37 ` William Breathitt Gray
2019-09-05 14:10 ` Tony Lindgren
2019-09-08 11:16 ` Jonathan Cameron [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=20190908121618.3e7e5618@archlinux \
--to=jic23@kernel.org \
--cc=bcousson@baylibre.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=vilhelm.gray@gmail.com \
/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).