linux-kernel - Re: [GIT PATCH] STAGING fixes for 2.6.31-rc2-git tree

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] [day] [month] [year] [list]

Message-ID: <20090712230435.GA18177@kroah.com>
Date:	Sun, 12 Jul 2009 16:04:35 -0700
From:	Greg KH <greg@...ah.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Linus Torvalds <torvalds@...l.org>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] STAGING fixes for 2.6.31-rc2-git tree

On Sun, Jul 12, 2009 at 03:49:49PM -0700, David Rientjes wrote:
> On Sun, 12 Jul 2009, Greg KH wrote:
> 
> > Here are a few patches for the drivers/staging/ section of the kernel,
> > for your git tree.
> > 
> > The majority are fixes for things that people have reported, and now
> > there should not be any build errors for this portion of the tree.  If
> > anyone still has any problems, please let me know.
> > 
> 
> I do, the patch entitled "Staging: android: lowmemorykiller.c: fix it for 
> 'oom: move oom_adj value from task_struct to mm_struct'" was added to 
> gregkh-2.6 on July 2 and still hasn't made it to Linus' tree.  That has 
> caused a CONFIG_ANDROID_LOW_MEMORY_KILLER build failure for the last month 
> which I explicitly warned about over two months ago:
> 
> 	http://marc.info/?l=linux-kernel&m=124207736216807

Ah, sorry about that, I'll queue it up for the next round of patches to
go to Linus in a week or so.

Thanks for letting me know.

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/