[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL3PxMqzgza_GSBVVTuzh1u1EH=h=Zce4VF-xftY9f30ANnGSQ@mail.gmail.com>
Date: Sun, 8 Nov 2020 22:34:41 +0800
From: 廖威雄 <gmpy.liaowx@...il.com>
To: Christoph Hellwig <hch@....de>
Cc: Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>,
WeiXiong Liao <liaoweixiong@...winnertech.com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: simplify pstore-blk
hi Christoph,
On Fri, Oct 16, 2020 at 9:27 PM Christoph Hellwig <hch@....de> wrote:
>
> Hi all,
>
> this series cleans up and massively simplifies the pstore-blk code,
> please take a look.
Thanks for your code. I am going to redesign pstore/blk referred to
your idea.
I want to split pstore/blk into two parts, pstore/dev and pstore/blk.
pstore/dev is a common layer that handles all configurations
for users. All devices including block devices, ram devices and
mtd devices register to pstore/dev with operations and some flags.
Besides that, we can delete the codes for the block device to
register a panic_wirte() interface since there is no block device
needed. But it should be easy to implement registering if necessary.
Powered by blists - more mailing lists