linux-kernel - Re: [GIT PULL] staging: Android updates

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: <4F57D739.50603@fifo99.com>
Date:	Wed, 07 Mar 2012 13:46:34 -0800
From:	Daniel Walker <dwalker@...o99.com>
To:	John Stultz <john.stultz@...aro.org>
CC:	Greg KH <gregkh@...uxfoundation.org>,
	Android Kernel Team <kernel-team@...roid.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] staging: Android updates

On 03/07/2012 01:34 PM, John Stultz wrote:
>        android: ram_console: move footer strings
>        android: ram_console: drop early buffer support
>        android: ram_console: drop verbose ram_console support
>        android: ram_console: split out persistent ram

What are the differences between mtdoops/ramoops and ram_console? My 
research showed they had different ways of saving the memory, but didn't 
very similar things.

Daniel
--
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/