From: Thierry Reding <thierry.reding@gmail.com>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: Stefan Agner <stefan@agner.ch>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] pwm: ftm: fix clock enable/disable when using PM
Date: Mon, 23 Nov 2015 10:49:55 +0100 [thread overview]
Message-ID: <20151123094955.GA31868@ulmo.nvidia.com> (raw)
In-Reply-To: <564E6B6D.80006@mleia.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Fri, Nov 20, 2015 at 02:38:05AM +0200, Vladimir Zapolskiy wrote:
> On 19.11.2015 04:04, Stefan Agner wrote:
> > Thierry,
> >
> > I realized that this patch did not make it into 4.4-rc1, while others,
> > IMHO less important patches which have been posted later (e.g. sunxi
> > whitespace fixes) have made it! :-(
> >
> > Anything wrong with that? Or am I on your spam list? Note that this is
> > already a RESEND :-)
>
> You are not alone with this problem, I have unreviewed changes in
> linux-pwm mailing list sent in 2014 :)
Please either ping me or resend patches if I don't reply within a week
or so. Chances are I've either not seen them or meant to reply but never
got around to.
Also, the Linux kernel is a community-driven project, so I fully expect
contributors to review each other's patches. Review isn't something that
only maintainers need to do.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-23 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 4:29 [PATCH RESEND] pwm: ftm: fix clock enable/disable when using PM Stefan Agner
2015-11-19 2:04 ` Stefan Agner
2015-11-20 0:38 ` Vladimir Zapolskiy
2015-11-23 9:49 ` Thierry Reding [this message]
2015-11-23 9:45 ` Thierry Reding
2015-11-23 21:40 ` Stefan Agner
2015-11-23 21:47 ` Stefan Agner
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=20151123094955.GA31868@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=stefan@agner.ch \
--cc=vz@mleia.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