From: Greg KH <greg@kroah.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: Chris Wright <chrisw@sous-sol.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Sanjeev Premi <premi@ti.com>, Kyle Manna <kyle@kylemanna.com>,
stable@vger.kernel.org
Subject: Re: Several MFD patches for stable
Date: Tue, 3 Jan 2012 08:16:56 -0800 [thread overview]
Message-ID: <20120103161656.GA25909@kroah.com> (raw)
In-Reply-To: <4F031233.7040007@compulab.co.il>
On Tue, Jan 03, 2012 at 04:35:31PM +0200, Igor Grinberg wrote:
> Hi Greg, Chris,
>
> I've found several MFD patches that I think should have been
> applied also to stable, but they hadn't been applied
> (probably because nobody cared to send them to stable@vger.kernel.org).
>
> The patches are upstream:
> e178ccb33569da17dc897a08a3865441b813bdfb (mfd: Fix mismatch in twl4030 mutex lock-unlock)
> 66cc5b8e50af87b0bbd0f179d76d2826f4549c13 (mfd: Copy the device pointer to the twl4030-madc structure)
> d0e84caeb4cd535923884735906e5730329505b4 (mfd: Check for twl4030-madc NULL pointer)
> 3d6271f92e98094584fd1e609a9969cd33e61122 (mfd: Turn on the twl4030-madc MADC clock)
>
> I don't know what is right flow that I should follow
> to get those into the stable tree.
Read Documentation/stable_kernel_rules.txt for how to do this (hint, you
did it properly, with a only few minor things missed.)
What kernel version(s) do you want these applied to? What order should
they be applied in?
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-03 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 14:35 Several MFD patches for stable Igor Grinberg
2012-01-03 16:16 ` Greg KH [this message]
2012-01-03 21:01 ` Greg KH
2012-01-05 8:07 ` Igor Grinberg
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=20120103161656.GA25909@kroah.com \
--to=greg@kroah.com \
--cc=chrisw@sous-sol.org \
--cc=grinberg@compulab.co.il \
--cc=kyle@kylemanna.com \
--cc=linux-kernel@vger.kernel.org \
--cc=premi@ti.com \
--cc=sameo@linux.intel.com \
--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.