From: Andrew Lunn <andrew@lunn.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
aditya@kobol.io,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Jason Cooper <jason@lakedaemon.net>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Richard Genoud <richard.genoud@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>,
gauthier@kobol.io, Alban Browaeys <alban.browaeys@gmail.com>,
linux-pwm@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dennis Gilmore <dennis@ausil.us>,
Ralph Sennhauser <ralph.sennhauser@gmail.com>
Subject: Re: [PATCH RESEND 1/2] gpio: mvebu: Add support for multiple PWM lines per GPIO chip
Date: Wed, 29 Aug 2018 14:52:09 +0200 [thread overview]
Message-ID: <20180829125209.GB1955@lunn.ch> (raw)
In-Reply-To: <CACRpkdZU36s=-G7ncW3JMb+vXDmpdLO+3zupQD_fwUyfZxx4vA@mail.gmail.com>
> Thanks yes Andrew is involved, I will wait for Andrew's definitive ACK
> before merging any of this.
Hi Linus
Given the review comments i made so far, it has a NACK.
I will happily review the next version.
Andrew
next prev parent reply other threads:[~2018-08-29 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 2:29 [PATCH RESEND 0/2] gpio: mvebu: Add support for multiple PWM lines Aditya Prayoga
2018-08-06 2:29 ` [PATCH RESEND 1/2] gpio: mvebu: Add support for multiple PWM lines per GPIO chip Aditya Prayoga
2018-08-06 3:38 ` Andrew Lunn
2018-08-08 10:27 ` Aditya Prayoga
2018-08-29 7:54 ` Linus Walleij
2018-08-29 8:02 ` Thomas Petazzoni
2018-08-29 12:09 ` Linus Walleij
2018-08-29 12:52 ` Andrew Lunn [this message]
2018-08-29 8:13 ` Gregory CLEMENT
2018-08-06 2:29 ` [PATCH RESEND 2/2] gpio: mvebu: Allow to use non-default PWM counter Aditya Prayoga
2018-08-06 13:52 ` Andrew Lunn
2018-08-08 11:40 ` Aditya Prayoga
2018-08-09 15:03 ` Richard Genoud
2018-08-09 15:43 ` Andrew Lunn
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=20180829125209.GB1955@lunn.ch \
--to=andrew@lunn.ch \
--cc=aditya@kobol.io \
--cc=alban.browaeys@gmail.com \
--cc=dennis@ausil.us \
--cc=gauthier@kobol.io \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=ralph.sennhauser@gmail.com \
--cc=richard.genoud@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas.petazzoni@free-electrons.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
all inboxes | Powered by JetHome®