From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: dream in staging: remove wakelock support
Date: Mon, 26 Oct 2009 16:42:47 -0700 [thread overview]
Message-ID: <20091026234247.GA26583@kroah.com> (raw)
In-Reply-To: <20091022090354.GA30695@elf.ucw.cz>
On Thu, Oct 22, 2009 at 11:03:54AM +0200, Pavel Machek wrote:
>
> Includes changed so that <linux/sched.h> is now needed for
> TASK_INTERRUPTIBLE and friends, so include it.
>
> Remove hooks for features not in mainline, such as earlysuspend and
> wakelocks.
>
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
Even after this patch, the code does not build at all.
I'm going to mark CONFIG_DREAM as BROKEN for now until the build errors
get resolved, is that fair?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Arve Hj?nnev?g <arve@android.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Brian Swetland <swetland@google.com>
Subject: Re: dream in staging: remove wakelock support
Date: Mon, 26 Oct 2009 16:42:47 -0700 [thread overview]
Message-ID: <20091026234247.GA26583@kroah.com> (raw)
In-Reply-To: <20091022090354.GA30695@elf.ucw.cz>
On Thu, Oct 22, 2009 at 11:03:54AM +0200, Pavel Machek wrote:
>
> Includes changed so that <linux/sched.h> is now needed for
> TASK_INTERRUPTIBLE and friends, so include it.
>
> Remove hooks for features not in mainline, such as earlysuspend and
> wakelocks.
>
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
Even after this patch, the code does not build at all.
I'm going to mark CONFIG_DREAM as BROKEN for now until the build errors
get resolved, is that fair?
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-26 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 9:03 dream in staging: remove wakelock support Pavel Machek
2009-10-22 9:03 ` Pavel Machek
2009-10-26 23:42 ` Greg KH [this message]
2009-10-26 23:42 ` Greg KH
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=20091026234247.GA26583@kroah.com \
--to=greg@kroah.com \
--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 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.