From: Thierry Reding <thierry.reding@gmail.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Andrew Davis <afd@ti.com>
Subject: Re: [PATCH v2 0/2] pwm-tiecap: Add support for AM654 SoCs
Date: Thu, 1 Nov 2018 10:56:40 +0100 [thread overview]
Message-ID: <20181101095640.GA23707@ulmo> (raw)
In-Reply-To: <e3d4afac-edc3-3b2a-3c75-8eb307705dd4@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Wed, Oct 31, 2018 at 07:02:23PM +0530, Vignesh R wrote:
> Hi Thierry,
>
> On 16/10/18 4:45 PM, Thierry Reding wrote:
> > On Tue, Oct 16, 2018 at 11:34:00AM +0530, Vignesh R wrote:
> >> Couple of patches to enable pwm-tiecap driver to be used with TI's new
> >> AM654 platforms.
> >>
> >> Vignesh R (2):
> >> dt-bindings: pwm: tiecap: Add TI AM654 SoC specific compatible
> >> pwm: Kconfig: Enable TI ECAP driver for ARCH_K3
> >>
> >> Documentation/devicetree/bindings/pwm/pwm-tiecap.txt | 1 +
> >> drivers/pwm/Kconfig | 5 ++---
> >> 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > Applied, thanks.
> >
>
> I could not see this patch series in pwm tree here:
> https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git
> Is this queued for v4.20?
I forgot to push out those patches to for-next. Done that now. It's
quite late for those to go in, but since these don't touch any code
it looks okay.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] pwm-tiecap: Add support for AM654 SoCs
Date: Thu, 1 Nov 2018 10:56:40 +0100 [thread overview]
Message-ID: <20181101095640.GA23707@ulmo> (raw)
In-Reply-To: <e3d4afac-edc3-3b2a-3c75-8eb307705dd4@ti.com>
On Wed, Oct 31, 2018 at 07:02:23PM +0530, Vignesh R wrote:
> Hi Thierry,
>
> On 16/10/18 4:45 PM, Thierry Reding wrote:
> > On Tue, Oct 16, 2018 at 11:34:00AM +0530, Vignesh R wrote:
> >> Couple of patches to enable pwm-tiecap driver to be used with TI's new
> >> AM654 platforms.
> >>
> >> Vignesh R (2):
> >> dt-bindings: pwm: tiecap: Add TI AM654 SoC specific compatible
> >> pwm: Kconfig: Enable TI ECAP driver for ARCH_K3
> >>
> >> Documentation/devicetree/bindings/pwm/pwm-tiecap.txt | 1 +
> >> drivers/pwm/Kconfig | 5 ++---
> >> 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > Applied, thanks.
> >
>
> I could not see this patch series in pwm tree here:
> https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git
> Is this queued for v4.20?
I forgot to push out those patches to for-next. Done that now. It's
quite late for those to go in, but since these don't touch any code
it looks okay.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181101/8625f6a5/attachment.sig>
next prev parent reply other threads:[~2018-11-01 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 6:04 [PATCH v2 0/2] pwm-tiecap: Add support for AM654 SoCs Vignesh R
2018-10-16 6:04 ` Vignesh R
2018-10-16 6:04 ` Vignesh R
2018-10-16 6:04 ` [PATCH v2 1/2] dt-bindings: pwm: tiecap: Add TI AM654 SoC specific compatible Vignesh R
2018-10-16 6:04 ` Vignesh R
2018-10-16 6:04 ` Vignesh R
2018-10-16 6:04 ` [PATCH v2 2/2] pwm: Kconfig: Enable TI ECAP driver for ARCH_K3 Vignesh R
2018-10-16 6:04 ` Vignesh R
2018-10-16 6:04 ` Vignesh R
2018-10-16 11:15 ` [PATCH v2 0/2] pwm-tiecap: Add support for AM654 SoCs Thierry Reding
2018-10-16 11:15 ` Thierry Reding
2018-10-31 13:32 ` Vignesh R
2018-10-31 13:32 ` Vignesh R
2018-10-31 13:32 ` Vignesh R
2018-11-01 9:56 ` Thierry Reding [this message]
2018-11-01 9:56 ` Thierry Reding
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=20181101095640.GA23707@ulmo \
--to=thierry.reding@gmail.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.