From: Igor Grinberg <grinberg@compulab.co.il>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: ARM: OMAP: patches for stable
Date: Fri, 24 Feb 2012 10:43:25 +0200 [thread overview]
Message-ID: <4F474DAD.1030302@compulab.co.il> (raw)
Hi Greg,
There are several patches already in mainline, that should be also applied to stable:
40410715 (ARM: omap: fix oops in drivers/video/omap2/dss/dpi.c) [3.2-stable]
d980e0f8 (ARM: omap: fix oops in arch/arm/mach-omap2/vp.c when pmic is not found) [3.2-stable]
Can these, please be applied to stable?
Thanks
--
Regards,
Igor.
WARNING: multiple messages have this Message-ID (diff)
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: OMAP: patches for stable
Date: Fri, 24 Feb 2012 10:43:25 +0200 [thread overview]
Message-ID: <4F474DAD.1030302@compulab.co.il> (raw)
Hi Greg,
There are several patches already in mainline, that should be also applied to stable:
40410715 (ARM: omap: fix oops in drivers/video/omap2/dss/dpi.c) [3.2-stable]
d980e0f8 (ARM: omap: fix oops in arch/arm/mach-omap2/vp.c when pmic is not found) [3.2-stable]
Can these, please be applied to stable?
Thanks
--
Regards,
Igor.
next reply other threads:[~2012-02-24 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 8:43 Igor Grinberg [this message]
2012-02-24 8:43 ` ARM: OMAP: patches for stable Igor Grinberg
2012-02-27 21:14 ` Greg Kroah-Hartman
2012-02-27 21:14 ` Greg Kroah-Hartman
2012-02-27 21:19 ` Russell King - ARM Linux
2012-02-27 21:19 ` Russell King - ARM Linux
2012-02-27 21:27 ` Greg Kroah-Hartman
2012-02-27 21:27 ` Greg Kroah-Hartman
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=4F474DAD.1030302@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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.