lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091029010419.GA18410@suse.de>
Date:	Wed, 28 Oct 2009 18:04:19 -0700
From:	Greg KH <gregkh@...e.de>
To:	Bryan Wu <bryan.wu@...onical.com>
Cc:	Brian Swetland <swetland@...gle.com>,
	Eric Miao <eric.miao@...onical.com>,
	kernel-team@...ts.ubuntu.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: Android logger: fix compiling error

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,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ