All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: srinivas.kandagatla@linaro.org, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "regulator: qcom_smd: add list_voltage callback" has been added to the 4.6-stable tree
Date: Mon, 11 Jul 2016 19:09:47 -0700	[thread overview]
Message-ID: <20160712020947.GA11787@kroah.com> (raw)
In-Reply-To: <20160712002634.GC9976@sirena.org.uk>

On Tue, Jul 12, 2016 at 01:26:34AM +0100, Mark Brown wrote:
> On Mon, Jul 11, 2016 at 04:39:10PM -0700, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     regulator: qcom_smd: add list_voltage callback
> > 
> > to the 4.6-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      regulator-qcom_smd-add-list_voltage-callback.patch
> > and it can be found in the queue-4.6 subdirectory.
> 
> There's a subsequent patch, 43160ffd12 (regulator: qcom_smd: Remove
> list_voltage callback for rpm_smps_ldo_ops_fixed) which is also needed
> for some of the users (this was only reported to me a couple of hours
> ago so I've still not sent that patch to Linus yet, should happen
> tomorrow).  That looks like a cleanup but in fact fixes some booting
> issues that some devices see.

Ok, if it lands tomorrow or so, that should be fine, I'm not counting on
doing a stable release for the next few days at the earliest.

thanks,

greg k-h

      reply	other threads:[~2016-07-12  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 23:39 Patch "regulator: qcom_smd: add list_voltage callback" has been added to the 4.6-stable tree gregkh
2016-07-12  0:26 ` Mark Brown
2016-07-12  2:09   ` Greg KH [this message]

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=20160712020947.GA11787@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.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 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.