From: Greg KH <gregkh@linuxfoundation.org>
To: Russ Dill <Russ.Dill@ti.com>
Cc: Jonghwan Choi <jhbird.choi@samsung.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"'Mark Brown'" <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 3.8-stable] regulator: core: Log when a device causes a voltage
Date: Tue, 2 Apr 2013 13:54:51 -0700 [thread overview]
Message-ID: <20130402205451.GA2710@kroah.com> (raw)
In-Reply-To: <515B41EA.8040704@ti.com>
On Tue, Apr 02, 2013 at 01:39:06PM -0700, Russ Dill wrote:
> On 04/02/2013 01:02 PM, Greg KH wrote:
> > On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
> >> 3.8-stable review patch. If anyone has any objections, please let us know.
> >>
> >> ------------------
> >>
> >> From: "Russ Dill <Russ.Dill@ti.com>"
> >>
> >> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
> >
> > Wait, no, this is NOT the commit id of this patch, please don't get this
> > wrong.
> >
> > I've dropped this from my stable mbox, if Russ feels this should go to
> > 3.8-stable, please send me the correct git id of the patch to apply.
>
> 9c7b4e8a8ad2624106fbf690fa97ab9c8c9bfa88 is the proper upstream commit.
> This fixes a potential oops that was added in 3.8-rc4, and fixed
> upstream in 3.9-rc1. I do think it belongs in stable.
Thanks, I've applied that commit now.
> Too bad I can't muck up the commit, then I'd owe you a beer. Might help
> that shoulder of yours.
Yes, that would help it out, but probably not help me catch up with
pending patches to apply :)
greg k-h
next prev parent reply other threads:[~2013-04-02 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 9:30 [PATCH 3.8-stable] regulator: core: Log when a device causes a voltage Jonghwan Choi
2013-04-02 18:44 ` Greg KH
2013-04-02 20:02 ` Greg KH
2013-04-02 20:39 ` Russ Dill
2013-04-02 20:54 ` Greg KH [this message]
2013-04-02 23:32 ` Jonghwan Choi
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=20130402205451.GA2710@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Russ.Dill@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jhbird.choi@samsung.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox