From: Greg KH <gregkh@linuxfoundation.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Rom Lemarchand <romlem@google.com>,
Mark Salyzyn <salyzyn@google.com>,
Kees Cook <keescook@chromium.org>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH 2/2][RFC] staging: Remove the Android logger driver
Date: Wed, 21 Jan 2015 06:01:23 +0800 [thread overview]
Message-ID: <20150120220123.GA15097@kroah.com> (raw)
In-Reply-To: <1421790155-3309-2-git-send-email-john.stultz@linaro.org>
On Tue, Jan 20, 2015 at 01:42:35PM -0800, John Stultz wrote:
> With the relase of Lollipop, Android no longer
> requires the logger driver.
>
> There are three patches which the android dev's
> still need before they drop logger on all their
> devices:
>
> [PATCH v3 1/3] pstore: use scnprintf
> [PATCH 2/3] pstore: remove superfluous memory size check
> [PATCH v2 3/3] pstore: add pmsg
>
> But these seem to have been acked and are hopefully
> queued for upstream.
That's great news, are these pstore patches in linux-next already? If
so, I'll be glad to queue this up for 3.20.
thanks,
greg k-h
next prev parent reply other threads:[~2015-01-20 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 21:42 [PATCH 1/2][RFC] staging: Remove the Android alarm-dev driver John Stultz
2015-01-20 21:42 ` [PATCH 2/2][RFC] staging: Remove the Android logger driver John Stultz
2015-01-20 22:01 ` Greg KH [this message]
2015-01-25 12:11 ` Greg KH
2015-01-26 20:07 ` [PATCH] " John Stultz
2015-01-27 9:28 ` Paul Bolle
2015-01-27 9:24 ` [PATCH 1/2][RFC] staging: Remove the Android alarm-dev driver Paul Bolle
2015-01-27 15:06 ` John Stultz
2015-01-27 15:22 ` [PATCH] staging: Remove logger and alarm-dev from android Makefile John Stultz
2015-01-27 17:16 ` Kees Cook
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=20150120220123.GA15097@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romlem@google.com \
--cc=salyzyn@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 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.