From: liaoweixiong <liaoweixiong@allwinnertech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v10 0/4] pstore/block: new support logger for block devices
Date: Wed, 27 Feb 2019 08:50:18 +0800 [thread overview]
Message-ID: <34916ace-7020-06e8-7958-f3652aef6604@allwinnertech.com> (raw)
In-Reply-To: <20190226112033.GA16900@kroah.com>
On 2019-02-26 19:20, Greg Kroah-Hartman wrote:
> On Tue, Feb 26, 2019 at 02:33:41PM +0800, liaoweixiong wrote:
>> Why should we need pstore_block?
>> 1. Most embedded intelligent equipment have no persistent ram, which
>> increases costs. We perfer to cheaper solutions, like block devices.
>> In fast, there is already a sample for block device logger in driver
>> MTD (drivers/mtd/mtdoops.c).
>> 2. Do not any equipment have battery, which means that it lost all data
>> on general ram if power failure. Pstore has little to do for these
>> equipments.
>>
>> [PATCH v10]
>
> Why are you still labeling these as "RFC"? No one should actually be
> applying a Request For Comments patchset, as you obviously are not
> thinking it is ready to be merged :(
>
> After 10 revisions, I hope you are confident in this patchset :)
>
I'm confident in this patchset :) . It is first time for me to submit
RFC patches, i just don't know i should change the label to PATCH. Thank
you for reminding me.
> thanks,
>
> greg k-h
>
--
liaoweixiong
prev parent reply other threads:[~2019-02-27 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 6:33 liaoweixiong
2019-02-26 6:33 ` [RFC v10 1/4] pstore/blk: " liaoweixiong
2019-02-26 6:33 ` [RFC v10 2/4] pstore/blk: add blkoops for pstore_blk liaoweixiong
2019-02-26 6:33 ` [RFC v10 3/4] pstore/blk: support pmsg for pstore block liaoweixiong
2019-02-26 6:33 ` [RFC v10 4/4] Documentation: pstore/blk: create document for pstore_blk liaoweixiong
2019-02-26 11:20 ` [RFC v10 0/4] pstore/block: new support logger for block devices Greg Kroah-Hartman
2019-02-27 0:50 ` liaoweixiong [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=34916ace-7020-06e8-7958-f3652aef6604@allwinnertech.com \
--to=liaoweixiong@allwinnertech.com \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®