From: Bryan Wu <bryan.wu@canonical.com>
To: Greg KH <gregkh@suse.de>
Cc: Brian Swetland <swetland@google.com>,
Eric Miao <eric.miao@canonical.com>,
kernel-team@lists.ubuntu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: Android logger: fix compiling error
Date: Thu, 29 Oct 2009 09:11:39 +0800 [thread overview]
Message-ID: <4AE8EBCB.5030102@canonical.com> (raw)
In-Reply-To: <20091029010419.GA18410@suse.de>
Greg KH wrote:
> On Thu, Oct 29, 2009 at 09:01:07AM +0800, Bryan Wu wrote:
>> Greg KH wrote:
>>> On Tue, Oct 27, 2009 at 12:40:07PM +0800, Eric Miao wrote:
>>>>> Compiling broke since commit a99bbaf5ee6bad1aca0c88ea65ec6e5373e86184
>>>>> headers: remove sched.h from poll.h
>>>>>
>>>>> Adding <linux/sched.h> to fix this compiling bug.
>>> I have now just marked the android drivers as broken, as this is not the
>>> only build error in them at the moment :(
>>>
>> Yeah, actually the drivers/staging/android/lowmemorykiller.c has been
>> failing to compile for a long time, because that struct mm_struct does
>> not have a field named oom_adj. All the Android drivers are compiled
>> as modules in Ubuntu kernel package, except this one.
>>
>> Although Android public kernel is still in 2.6.29, it's own driver is
>> totally different with our mainline staging version. Is there any plan
>> to sync with it?
>
> No, Google has abandoned any current effort to push code upstream for
> the past year :(
>
> The android drivers are deleted in linux-next and will go away in 2.6.33
> because of this.
>
Thanks a lot for this update. It looks like we need to consider to drop Android
modules in our Ubuntu kernel building somehow.
Cheers,
-Bryan
next prev parent reply other threads:[~2009-10-29 1:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 16:52 [PATCH] Staging: Android logger: fix compiling error Bryan Wu
2009-10-27 4:40 ` Eric Miao
2009-10-27 4:42 ` Bryan Wu
2009-10-27 14:05 ` Greg KH
2009-10-29 1:01 ` Bryan Wu
2009-10-29 1:04 ` Greg KH
2009-10-29 1:11 ` Bryan Wu [this message]
2009-10-29 1:17 ` Greg KH
2009-10-29 1:27 ` Bryan Wu
2009-10-29 1:28 ` Greg KH
2009-10-29 1:55 ` Bryan Wu
2009-10-29 2:22 ` Brian Swetland
2009-10-30 14:08 ` Pavel Machek
2009-11-01 16:40 ` Bryan Wu
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=4AE8EBCB.5030102@canonical.com \
--to=bryan.wu@canonical.com \
--cc=eric.miao@canonical.com \
--cc=gregkh@suse.de \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
/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