In case of the last page containing bitflips (ret > 0),
spinand_mtd_read() will return that number of bitflips for the last
page. But to me it looks like it should instead return max_bitflips like
it does when the last page read returns with 0.
Signed-off-by: Weixiong Liao
Reviewed-by: Boris Brez
Hi Miquel,
On 2019/6/28 AM2:17, Miquel Raynal wrote:
> Hi Miquel,
>
> Miquel Raynal wrote on Thu, 27 Jun 2019
> 19:06:44 +0200:
>
>> Hello,
>>
>> Schrempf Frieder wrote on Tue, 25 Jun
>> 2019 07:04:06 +:
>>
>>> Hi liaoweixiong,
>&g
In case of the last page containing bitflips (ret > 0),
spinand_mtd_read() will return that number of bitflips for the last
page. But to me it looks like it should instead return max_bitflips like
it does when the last page read returns with 0.
Signed-off-by: liaoweixiong
Reviewed-by: Bo
Oh, i am sorry that i had misunderstanded your letter.
Thank you for your document and guidance.
On 2019/6/25 PM 3:04, Schrempf Frieder wrote:
> Hi liaoweixiong,
>
> On 25.06.19 05:08, Greg KH wrote:
>> On Tue, Jun 25, 2019 at 09:02:29AM +0800, liaoweixiong wrote:
>>>
In case of the last page containing bitflips (ret > 0),
spinand_mtd_read() will return that number of bitflips for the last
page. But to me it looks like it should instead return max_bitflips like
it does when the last page read returns with 0.
Signed-off-by: liaoweixiong
Reviewed-by: Bo
Um.. I am sorry. It is the first time for me to resend patch.
I will send this patch again with correct tags.
On 2019/6/24 PM10:47, Schrempf Frieder wrote:
> On 24.06.19 14:15, liaoweixiong wrote:
>> In case of the last page containing bitflips (ret > 0),
>> spinand_mtd_read(
In case of the last page containing bitflips (ret > 0),
spinand_mtd_read() will return that number of bitflips for the last
page. But to me it looks like it should instead return max_bitflips like
it does when the last page read returns with 0.
Signed-off-by: liaoweixiong
Acked-by: Bo
OK, thanks for your reviewing. I will resend right now.
On 2019/6/24 PM3:37, Schrempf Frieder wrote:
> On 20.06.19 03:00, liaoweixiong wrote:
>> In case of the last page containing bitflips (ret > 0),
>> spinand_mtd_read() will return that number of bitflips for the last
>
In case of the last page containing bitflips (ret > 0),
spinand_mtd_read() will return that number of bitflips for the last
page. But to me it looks like it should instead return max_bitflips like
it does when the last page read returns with 0.
Signed-off-by: liaoweixiong
---
drivers/mtd/n
hi Boris Brezillon,
Sure, i will adjust the commit message and send again right now.
On 2019/6/20 AM12:18, Boris Brezillon wrote:
> On Wed, 19 Jun 2019 14:02:14 +
> Schrempf Frieder wrote:
>
>> On 19.06.19 15:46, Boris Brezillon wrote:
>>> Hi liaoweixiong,
>>&
In function spinand_mtd_read, if the last page to read occurs bitflip,
this function will return error value because veriable ret not equal to 0.
Signed-off-by: liaoweixiong
---
drivers/mtd/nand/spi/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/spi
similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig |8 +
fs/pstore/Makefile |3 +
fs/pstore/blkzone.c
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 233 +
MAINTAINERS
' haven't be exproted yet, so we use
'kernel_read' and 'kernel_write' instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well
e parameter
is valid. Otherwise, it can only record data to ram buffer, which will
be dropped when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS| 2 +-
fs/pstore/Kconfig | 102 +++
fs/pstore/Makefile | 2 +
fs/pstore/bl
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 18
fs/pstore/blkoops.c| 10 ++
fs/pstore/blkzone.c| 256 +
include/linux/pstore_blk.h | 1
Hi,
On 2019-03-06 09:16, Randy Dunlap wrote:
> Hi,
>
> On 2/27/19 11:12 PM, liaoweixiong wrote:
>> diff --git a/fs/pstore/Kconfig b/fs/pstore/Kconfig
>> index 7dfe00b..b417bf5 100644
>> --- a/fs/pstore/Kconfig
>> +++ b/fs/pstore/Kconfig
>> @@ -210,6 +210
Hi,
I will fix all on next version. Thank you very much.
On 2019-03-06 09:14, Randy Dunlap wrote:
> Hi,
>
> On 2/27/19 11:12 PM, liaoweixiong wrote:
>> diff --git a/fs/pstore/Kconfig b/fs/pstore/Kconfig
>> index defcb75..7dfe00b 100644
>> --- a/fs/pstore/Kconfig
hi Dan Carpenter,
On 2019/03/05 15:12, Dan Carpenter wrote:
> Hi liaoweixiong,
>
> url:
> https://github.com/0day-ci/linux/commits/liaoweixiong/pstore-block-new-support-logger-for-block-devices/20190303-142003
> base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/l
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 21
fs/pstore/blkoops.c| 10 ++
fs/pstore/blkzone.c| 253 +
include/linux/pstore_blk.h | 1
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 233 +
MAINTAINERS
e parameter
is valid. Otherwise, it can only record data to ram buffer, which will
be dropped when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS| 2 +-
fs/pstore/Kconfig | 114 ++
fs/pstore/Makefile | 2 +
fs/pstore/bl
similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig |8 +
fs/pstore/Makefile |3 +
fs/pstore/blkzone.c
vfs_write' haven't be exproted yet, so we use
'kernel_read' and 'kernel_write' instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well o
Thank you for your correction. I will update the patch in the 12th version.
On 2019/02/28 13:15, Randy Dunlap wrote:
> On 2/19/19 3:52 AM, liaoweixiong wrote:
>> The document, at Documentation/admin-guide/pstore-block.rst,
>> tells user how to use pstore_blk and the attentions abou
e parameter
is valid. Otherwise, it can only record data to ram buffer, which will
be dropped when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS| 2 +-
fs/pstore/Kconfig | 114 ++
fs/pstore/Makefile | 2 +
fs/pstore/bl
similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig |8 +
fs/pstore/Makefile |3 +
fs/pstore/blkzone.c
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 21
fs/pstore/blkoops.c| 10 ++
fs/pstore/blkzone.c| 253 +
include/linux/pstore_blk.h | 1
; instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rathe
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 233 +
MAINTAINERS
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
e parameter
is valid. Otherwise, it can only record data to ram buffer, which will
be dropped when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS| 2 +-
fs/pstore/Kconfig | 114 ++
fs/pstore/Makefile | 2 +
fs/pstore/bl
module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rather than block device.
liaoweixiong (4):
pstore/blk: ne
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 233 +
MAINTAINERS
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 21
fs/pstore/blkoops.c| 10 ++
fs/pstore/blkzone.c| 253 +
include/linux/pstore_blk.h | 1
similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig |8 +
fs/pstore/Makefile |3 +
fs/pstore/blkzone.c
On 2019-02-22 23:36, Rob Herring wrote:
> +boot-architecture list
>
> On Tue, Feb 19, 2019 at 07:52:47PM +0800, liaoweixiong wrote:
>> Create DT binding document for blkoops.
>>
>> Signed-off-by: liaoweixiong
>> ---
>> .../devicetree/b
similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig |8 +
fs/pstore/Makefile |3 +
fs/pstore/blkzone.c
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 233 +
MAINTAINERS
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 21
fs/pstore/blkoops.c| 11 ++
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1
t;
on dts or "blkdev" on module parameter is valid.
Otherwise, it can only record data to ram buffer, which will be dropped
when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS| 2 +-
fs/pstore/Kconfig | 114
fs/pstore/Makefile
Create DT binding document for blkoops.
Signed-off-by: liaoweixiong
---
.../devicetree/bindings/pstore/blkoops.txt | 53 ++
MAINTAINERS| 1 +
2 files changed, 54 insertions(+)
create mode 100644 Documentation/devicetree
nd 'vfs_write'
Both of 'vfs_read' and 'vfs_write' haven't be exproted yet, so we use
'kernel_read' and 'kernel_write' instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_regis
On 2019-02-14 04:30, Rob Herring wrote:
> On Wed, Feb 13, 2019 at 7:51 AM liaoweixiong
> wrote:
>>
>>
>> On 2019-01-31 00:07, Rob Herring wrote:> On Wed, Jan 23, 2019 at
>> 08:05:13PM +0800, liaoweixiong wrote:
>>>> Create DT binding document for b
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/blkoops.c| 11 ++
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1 +
3 files changed, 244 insertions(+), 22
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 227 +
MAINTAINERS
Create DT binding document for blkoops.
Signed-off-by: liaoweixiong
---
.../devicetree/bindings/pstore/blkoops.txt | 29 ++
MAINTAINERS| 1 +
2 files changed, 30 insertions(+)
create mode 100644 Documentation/devicetree
path" on dts or "part_path" on module parameter is valid.
Otherwise, it can only record data to ram buffer, which will be dropped
when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS | 2 +-
fs/pstore/Kconfig | 117 +
fs/pstore/Makefile |
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rather than block d
On 2019-01-31 00:07, Rob Herring wrote:> On Wed, Jan 23, 2019 at
08:05:13PM +0800, liaoweixiong wrote:
>> Create DT binding document for blkoops.
>>
>> Signed-off-by: liaoweixiong
>> ---
>> .../devicetree/bindings/pstore-block/blkoops.txt | 32
>> +
On 2019-02-13 04:54, Kees Cook wrote:
> On Wed, Jan 23, 2019 at 4:06 AM 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
On 2019-01-24 02:19, Aaro Koskinen wrote:
> Hi,
>
> On Sat, Jan 19, 2019 at 04:53:48PM +0800, liaoweixiong wrote:
>> On 2019-01-18 08:12, Kees Cook wrote:
>>>> MTD (drivers/mtd/mtdoops.c).
>>>
>>> Would mtdoops get dropped in favor of pstore/blk, or
On 2019-01-24 02:26, Aaro Koskinen wrote:
> Hi,
>
> On Wed, Jan 23, 2019 at 08:05:11PM +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 so
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/blkoops.c| 11 ++
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1 +
3 files changed, 244 insertions(+), 22
register' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rather than block device.
liaoweixiong (5):
pstore/blk: new support logger for block devices
dt-
Create DT binding document for blkoops.
Signed-off-by: liaoweixiong
---
.../devicetree/bindings/pstore-block/blkoops.txt | 32 ++
MAINTAINERS| 1 +
2 files changed, 33 insertions(+)
create mode 100644 Documentation/devicetree
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 227 +
MAINTAINERS
path" on dts or "part_path" on module parameter is valid.
Otherwise, it can only record data to ram buffer, which will be dropped
when reboot.
Signed-off-by: liaoweixiong
---
MAINTAINERS | 2 +-
fs/pstore/Kconfig | 117 +
fs/pstore/Makefile |
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
Resend this mail.
On 2019-01-18 08:17, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> To enable pmsg, just set pmsg_size when block device register blkzone.
>
> At first pass, this looks like a reasonable extension of blkzone. Is
>
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 227 +
MAINTAINERS
path" on dts or "part_path" on module parameter is valid.
Otherwise, it can only record data to ram buffer, which will be dropped
when reboot.
Signed-off-by: liaoweixiong
---
.../devicetree/bindings/pstore-block/blkoops.txt | 32 +++
MAINTAINERS
haven't be exproted yet, so we use
'kernel_read' and 'kernel_write' instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works w
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/blkoops.c| 11 ++
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1 +
3 files changed, 244 insertions(+), 22
resend this email.
On 2019-01-18 08:21, Kees Cook wrote:
> On Thu, Jan 17, 2019 at 4:15 PM Kees Cook wrote:
>>
>> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
>> wrote:
>>>
>>> It is a sample for pstore_blk, using general ram rather than block device.
>
On 2019-01-18 08:15, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> It is a sample for pstore_blk, using general ram rather than block device.
>> According to pstore_blk, the data will be saved to ram buffer if not
>> register device p
On 2019-01-18 08:12, Kees Cook wrote:
> On Mon, Jan 7, 2019 at 4:01 AM liaoweixiong
> wrote:
>>
>> pstore_blk is similar to pstore_ram, but dump log to block devices
>> rather than persistent ram.
>>
>> Why should we need pstore_blk?
>> 1. Most embedde
The documemt, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 226 +
MAINTAINERS
It is a sample for pstore_blk, using general ram rather than block device.
According to pstore_blk, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
fs/pstore
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_blk after block device is
ready.
pstore_blk works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1 +
2 files changed, 233 insertions(+), 22 deletions(-)
diff --git a/fs/pstore
#x27; and 'kernel_write' instead.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_ro
#x27;
[PATCH v1]
On patch 1:
Core codes of pstore_rom, which works well on allwinner(sunxi) platform.
On patch 2:
A sample for pstore_rom, using general ram rather than block device.
liaoweixiong (3):
pstore/rom: new support logger for block devices
pstore/rom: add sample for pstore_rom
To enable pmsg, just set pmsg_size when block device register romzone.
The pmsg have a single-boot lifetime, which means that zone of pmsg gets
wiped after its contents get copied out after boot.
Signed-off-by: liaoweixiong
---
fs/pstore/romzone.c| 194
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
fs/pstore
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_rom after block device is
ready.
pstore_rom works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
fs/pstore
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_rom after block device is
ready.
pstore_rom works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
x27;t be exproted yet, so we use
'kernel_read'
and 'kernel_write' instead.
liaoweixiong (2):
pstore/rom: new support logger for block devices
pstore/rom: add sample for pstore_rom
fs/pstore/Kconfig | 16 +
fs/pstore/Makefile
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
fs/pstore
.
[PATCH v2]
On patch 1:
Fix build as module error for redefinition of 'romz_unregister' and
'romz_register'
liaoweixiong (2):
pstore/rom: new support logger for block devices
pstore/rom: add sample for pstore_rom
fs/pstore/Kconfig | 16 +
fs/pstore/Makefile
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_rom after block device is
ready.
pstore_rom works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
manage the
partition as zones, which is similar to pstore_ram.
Recommend that, block driver register pstore_rom after block device is
ready.
pstore_rom works well on allwinner(sunxi) platform.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 7 +
fs/pstore/Makefile | 3 +
.
On patch 2:
A sample for pstore_rom, using general ram rather than block device.
liaoweixiong (2):
pstore/rom: new support logger for block devices
pstore/rom: add sample for pstore_rom
fs/pstore/Kconfig | 16 +
fs/pstore/Makefile | 5 +
fs/pstore/rombuf.c | 46
It is a sample for pstore_rom, using general ram rather than block device.
According to pstore_rom, the data will be saved to ram buffer if not
register device path and apis for panic. So, it can only used to dump
Oops and some things will not reboot.
Signed-off-by: liaoweixiong
---
fs/pstore
when set to 'M'.
So, this patch is going to turn them back to 'bool'.
Fixes: 58eb5b670747 ("pstore: fix crypto dependencies")
Acked-by: Kees Cook
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff -
Reference to commit 58eb5b670747 ("pstore: fix crypto dependencies"),
which fixed crypto dependencies of deflate, lzo, lz4 and lz4hc
compression, but omitted 842 and newer compression zstd from
commit 1021bcf44d0e ("pstore: add zstd compression support")
Signed-off-by: l
89 matches
Mail list logo
