stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: Andreas Kemnade <andreas@kemnade.info>,
	Tony Lindgren <tony@atomide.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pm@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
	Nishanth Menon <nm@ti.com>,
	vireshk@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] regulator: twl: voltage lists for vdd1/2 on twl4030
Date: Mon, 9 Sep 2019 15:04:18 +0100	[thread overview]
Message-ID: <20190909140418.GH2036@sirena.org.uk> (raw)
In-Reply-To: <CAHCN7xJ0RmRQwo3bSF6FoLjOtrg5YZAMD9+=332LMzLLR1qdDA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

On Mon, Sep 09, 2019 at 08:32:06AM -0500, Adam Ford wrote:

> I am not sure who the right maintainer is, but as of today, cpufreq
> for users of twl4030 on 5.3-RC8 is still broken without this patch.
> Is there any way it can be applied before the final release?

Ugh, this affects cpufreq :/  I hadn't realized, sorry.  At this
point it's probably a bit late to get it into the release, but it
is tagged for stable so if it doesn't make it in it will be in
one of the first stable releases.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-09-09 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 21:43 [PATCH v2] regulator: twl: voltage lists for vdd1/2 on twl4030 Andreas Kemnade
2019-08-15 10:47 ` Adam Ford
2019-09-09 13:32   ` Adam Ford
2019-09-09 13:59     ` Andreas Kemnade
2019-09-09 14:04     ` Mark Brown [this message]
2019-08-15 17:14 ` Applied "regulator: twl: voltage lists for vdd1/2 on twl4030" to the regulator tree 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=20190909140418.GH2036@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=aford173@gmail.com \
    --cc=andreas@kemnade.info \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=vireshk@kernel.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).