public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Rientjes <rientjes@google.com>
Cc: "Matthew D. Reuther" <mreuther@joust.gpcc.itd.umich.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: android lowmemorykiller breaks compile
Date: Mon, 27 Jul 2009 06:58:22 -0700	[thread overview]
Message-ID: <20090727135822.GA9037@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907261630420.17123@chino.kir.corp.google.com>

On Sun, Jul 26, 2009 at 04:33:57PM -0700, David Rientjes wrote:
> On Sun, 26 Jul 2009, Matthew D. Reuther wrote:
> 
> > I don't actually use Android, but I compile it just for giggles. With every one of the 2.6.31-rc releases, my compile breaks when it hits lowmemorykiller:
> > 
> > drivers/staging/android/lowmemorykiller.c: In function 'lowmem_shrink':
> > drivers/staging/android/lowmemorykiller.c:106: error: 'struct task_struct' has no member named 'oomkilladj'
> > make[3]: *** [drivers/staging/android/lowmemorykiller.o] Error 1
> > make[2]: *** [drivers/staging/android] Error 2
> > 
> > Maybe this should not be selectable for x86? Can't tell.
> > 
> 
> It's had a fix pending in Greg KH's staging tree for a couple months, 
> we're just waiting for it to be pushed to Linus.  Greg indicated he will 
> send it in his next staging pull.

Yes, sorry, was on vacation, will go to Linus in a day or so.

thanks for your patience,

greg k-h

  reply	other threads:[~2009-07-27 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 23:10 android lowmemorykiller breaks compile Matthew D. Reuther
2009-07-26 23:33 ` David Rientjes
2009-07-27 13:58   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-26 23:15 Matthew D. Reuther
2009-09-02 23:37 Matthew D. Reuther

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=20090727135822.GA9037@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mreuther@joust.gpcc.itd.umich.edu \
    --cc=rientjes@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