From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/2] mtd : Make the mtd_suspend return 0 if the suspend is not implemented
Date: Thu, 2 Feb 2012 20:21:13 +0000 [thread overview]
Message-ID: <20120202202113.GA17309@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201202021940.26552.rjw@sisk.pl>
On Thu, Feb 02, 2012 at 07:40:26PM +0100, Rafael J. Wysocki wrote:
> On Thursday, February 02, 2012, Artem Bityutskiy wrote:
> > On Mon, 2012-01-30 at 23:58 +0100, Rafael J. Wysocki wrote:
> > > Thanks, but is anyone actually going to push it to Linus any time soon?
> >
> > I agree, but I am not the maintainer so cannot answer. David Woodhouse
> > is aware of this, but I do not know when he gonna send the pull request.
>
> Well, the problem is being reported by more and more people, so I'd
> like to push the fix quickly.
>
> David, please let me know if you don't want me to include the $subject patch
> into the next PM fixes pull request. If I don't hear from you, I'll push it
> next week for -rc4.
I too have it in my tree as a patch which Artem sent me, as it's rather
fundamental to not oopsing the kernel when you suspend/resume on any ARM
platform.
next prev parent reply other threads:[~2012-02-02 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 8:12 [PATCH RFC 0/2] mtd updates Shubhrajyoti D
2012-01-23 8:12 ` [PATCH RFC 1/2] mtd : Prevent the NULL pointer access Shubhrajyoti D
2012-01-27 19:08 ` Brian Norris
2012-01-23 8:12 ` [PATCH RFC 2/2] mtd : Make the mtd_suspend return 0 if the suspend is not implemented Shubhrajyoti D
2012-01-24 8:09 ` Brian Norris
2012-01-24 8:52 ` Shubhrajyoti
2012-01-24 9:06 ` Russell King - ARM Linux
2012-01-25 5:16 ` Brian Norris
2012-01-30 11:45 ` Artem Bityutskiy
2012-01-30 22:58 ` Rafael J. Wysocki
2012-02-02 11:43 ` Artem Bityutskiy
2012-02-02 18:40 ` Rafael J. Wysocki
2012-02-02 20:21 ` Russell King - ARM Linux [this message]
2012-02-02 20:36 ` Rafael J. Wysocki
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=20120202202113.GA17309@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).