From: Thierry Reding <thierry.reding@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Doug Anderson <dianders@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Brian Norris <briannorris@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Heiko Stuebner <heiko@sntech.de>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: pwm: Fix regulator ramp delay for continuous mode
Date: Fri, 8 Jul 2016 18:41:49 +0200 [thread overview]
Message-ID: <20160708164149.GE1151@ulmo.ba.sec> (raw)
In-Reply-To: <20160704091344.GY6247@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On Mon, Jul 04, 2016 at 11:13:44AM +0200, Mark Brown wrote:
> On Mon, Jul 04, 2016 at 11:05:04AM +0200, Boris Brezillon wrote:
>
> > I understand, but can we still expect to have it in 4.8 (I mean,
> > assuming Thierry is okay taking the first 2 patching for 4.8 too)?
>
> Possibly - we are getting very close to the merge window now, I don't
> know what Thierry's policies are on applying things as the merge window
> gets near.
I don't have hard deadlines, especially not for new code that has zero
potential for regressing. I've now pulled that whole series into the PWM
tree.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-08 16:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 4:53 [PATCH] regulator: pwm: Fix regulator ramp delay for continuous mode Douglas Anderson
2016-06-28 10:32 ` Caesar Wang
[not found] ` <1467089591-7631-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-06-28 16:07 ` Brian Norris
2016-06-28 18:56 ` Mark Brown
[not found] ` <20160628185656.GU17217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-28 19:35 ` Doug Anderson
2016-06-28 18:52 ` Mark Brown
[not found] ` <20160628185244.GT17217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-06-28 19:31 ` Doug Anderson
[not found] ` <CAD=FV=UNMhDYy3r+4a4FF8Ndwt+qNuV7_pOC=kzoaUxLfYYp4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-28 19:53 ` Mark Brown
2016-07-01 8:06 ` Mark Brown
[not found] ` <20160701080614.GA9196-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-01 20:17 ` Doug Anderson
[not found] ` <CAD=FV=WKR_Fq6o34886RCY-T-6AKdRqFz9H1aTiRq7Zu=o8TWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-02 7:59 ` Mark Brown
2016-07-06 18:30 ` Doug Anderson
2016-07-07 8:17 ` Mark Brown
2016-07-02 15:47 ` Boris Brezillon
2016-07-04 8:53 ` Mark Brown
[not found] ` <20160704085336.GT6247-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-04 9:05 ` Boris Brezillon
2016-07-04 9:13 ` Mark Brown
2016-07-08 16:41 ` Thierry Reding [this message]
2016-07-06 12:27 ` Boris Brezillon
2016-07-06 18:31 ` Doug Anderson
2016-07-07 8:16 ` Mark Brown
2016-07-07 8:03 ` Mark Brown
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=20160708164149.GE1151@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
/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).