All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Android Kernel Team <kernel-team@android.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] staging: Android updates
Date: Wed, 07 Mar 2012 13:46:34 -0800	[thread overview]
Message-ID: <4F57D739.50603@fifo99.com> (raw)
In-Reply-To: <1331156046.2191.185.camel@work-vm>

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

      parent reply	other threads:[~2012-03-07 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 21:34 [GIT PULL] staging: Android updates John Stultz
2012-03-07 21:42 ` Greg KH
2012-03-07 21:52   ` John Stultz
2012-03-07 21:46 ` Daniel Walker [this message]

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=4F57D739.50603@fifo99.com \
    --to=dwalker@fifo99.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.