From: Greg KH <greg@kroah.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
sfr@canb.auug.org.au, akpm@linux-foundation.org,
rientjes@google.com
Subject: Re: [PATCH] linux-next: 20090929 - android driver build breaks
Date: Tue, 29 Sep 2009 08:33:22 -0700 [thread overview]
Message-ID: <20090929153322.GD5020@kroah.com> (raw)
In-Reply-To: <20090929152027.GC4373@linux.vnet.ibm.com>
On Tue, Sep 29, 2009 at 08:50:27PM +0530, Kamalesh Babulal wrote:
> Hi Greg,
>
> next-20090929 randconfig build breaks with
> CONFIG_ANDROID_LOW_MEMORY_KILLER=y
>
> drivers/staging/android/lowmemorykiller.c: In function 'lowmem_shrink':
> drivers/staging/android/lowmemorykiller.c:111: error: 'struct mm_struct' has no member named 'oom_adj'
> make[3]: *** [drivers/staging/android/lowmemorykiller.o] Error 1
>
> Commit 0753ba01e126020bf0f8150934903b48935b697d was reverted back,
> which moves back oom_adj from mm_struct to task_struct and commit
> 28b83c5193e7ab951e402252278f2cc79dc4d298 moved the oomkilladj
> from task_struct to signal_struct.
>
> Following patch reverts the changes introduced by commit
> a6a9f81ccc9f5c86ccc22bbed1960a57d0316e8b to
> drivers/staging/android/lowmemorykiller.c
Ick, what a mess. I'll queue this up, thanks.
greg k-h
next prev parent reply other threads:[~2009-09-29 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 4:04 linux-next: Tree for September 29 Stephen Rothwell
2009-09-29 15:20 ` [PATCH] linux-next: 20090929 - android driver build breaks Kamalesh Babulal
2009-09-29 15:33 ` Greg KH [this message]
2009-10-08 22:47 ` Greg KH
2009-10-08 23:24 ` David Rientjes
2009-10-08 23:28 ` Greg KH
2009-10-08 23:48 ` David Rientjes
2009-10-09 0:22 ` Greg KH
2009-10-11 9:05 ` Pavel Machek
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=20090929153322.GD5020@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
/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).