[PATCH v4] phram: Allow the user to set the erase page size.

-by: Joern Engel Link: https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=a...@mail.gmail.com/ [Guohua Zhong: fix token array index out of bounds and update patch for kernel master branch] Signed-off-by: Guohua Zhong --- v4: add three dash before changelog (v1, v2

[PATCH v3] phram: Allow the user to set the erase page size.

-by: Joern Engel Link: https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=a...@mail.gmail.com/ [Guohua Zhong: fix token array index out of bounds and update patch for kernel master branch] Signed-off-by: Guohua Zhong v3: update authorship for Patrick O'Grady

Re: Re: [PATCH v2] phram: Allow the user to set the erase page size.

On Mon, Dec 7, 2020 at 14:56 AM Guohua Zhong wrote: > >> Permit the user to specify the erase page size as a parameter. >> This solves two problems: > >> - phram can access images made by mkfs.jffs2. mkfs.jffs2 won't >> create images with erase sizes less than 8KiB

ping: [PATCH v2] phram: Allow the user to set the erase page size.

ping On 11/25/20, Guohua Zhong wrote: > Permit the user to specify the erase page size as a parameter. > This solves two problems: > > - phram can access images made by mkfs.jffs2. mkfs.jffs2 won't > create images with erase sizes less than 8KiB; many architectures > define

[PATCH v2] phram: Allow the user to set the erase page size.

: https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=a...@mail.gmail.com/ [Guohua Zhong: fix token array index out of bounds and update patch for kernel master branch] Signed-off-by: Guohua Zhong Reported-by: kernel test robot --- v2: fix build error which

[PATCH] phram: Allow the user to set the erase page size.

: https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=a...@mail.gmail.com/ [Guohua Zhong: fix token array index out of bounds and update patch for kernel master branch] Signed-off-by: Guohua Zhong --- drivers/mtd/devices/phram.c | 52

[PATCH] phram: Allow the user to set the erase page size.

: https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=a...@mail.gmail.com/ [Guohua Zhong: fix token array index out of bounds and update patch for kernel master branch] Signed-off-by: Guohua Zhong --- drivers/mtd/devices/phram.c | 51

Re: Re：Re: [PATCH] powerpc: Fix a bug in __div64_32 if divisor is zero

>> >In generic version in lib/math/div64.c, there is no checking of 'base' >> >either. >> >Do we really want to add this check in the powerpc version only ? >> >> >The only user of __div64_32() is do_div() in >> >include/asm-generic/div64.h. Wouldn't it be better to do the check there ? >> >>

Re: Re：Re: [PATCH] powerpc: Fix a bug in __div64_32 if divisor is zero

>> Yet, I have noticed that there is no checking of 'base' in these functions. >> But I am not sure how to check is better.As we know that the result is >> undefined when divisor is zero. It maybe good to print error and dump stack. >> Let the process to know that the divisor is zero by sending

Re：Re: [PATCH] powerpc: Fix a bug in __div64_32 if divisor is zero

>In generic version in lib/math/div64.c, there is no checking of 'base' >either. >Do we really want to add this check in the powerpc version only ? >The only user of __div64_32() is do_div() in >include/asm-generic/div64.h. Wouldn't it be better to do the check there ? >Christophe Yet, I have

Re: [PATCH] powerpc: Fix a bug in __div64_32 if divisor is zero

xists. >> >> So it is also a bug in the cputime_adjust which does not check if >> stime + utime = 0 >> >> time = scale_stime((__force u64)stime, (__force u64)rtime, >> (__force u64)(stime + utime)); >> >> The commit 3dc167ba5729

Re: [PATCH] powerpc: Fix a bug in __div64_32 if divisor is zero

xists. >> >> So it is also a bug in the cputime_adjust which does not check if >> stime + utime = 0 >> >> time = scale_stime((__force u64)stime, (__force u64)rtime, >> (__force u64)(stime + utime)); >> >> The commit 3dc167ba5729

[PATCH] powerpc: Fix a bug in __div64_32 if divisor is zero

or other situation. Signed-off-by: Guohua Zhong Fixes:14cf11af6cf6 "( powerpc: Merge enough to start building in arch/powerpc.)" Fixes:94b212c29f68 "( powerpc: Move ppc64 boot wrapper code over to arch/powerpc)" Cc: sta...@vger.kernel.org # v2.6.15+ --- arch/powerpc/boot/div6

[PATCH v2] HID: i2c-hid: set power sleep before shutdown

gned-off-by: Guohua Zhong <ghzh...@yifangdigital.com> --- drivers/hid/i2c-hid/i2c-hid.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c index 2e021ba..79406ae 100644 --- a/drivers/hid/i2c-hid/i2c-h

[PATCH v2] HID: i2c-hid: set power sleep before shutdown

gned-off-by: Guohua Zhong --- drivers/hid/i2c-hid/i2c-hid.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c index 2e021ba..79406ae 100644 --- a/drivers/hid/i2c-hid/i2c-hid.c +++ b/drivers/hid/i2c-hid/i2c-h

[PATCH] HID: i2c-hid: set power sleep before shutdown

f We touch the touchscreen or some other i2c hid device ,the power consumtion will be go up even when the device is in shutdown state. Though the root cause maybe a HW issue. But it seems that it is a good pratice to set power sleep for i2c-hid device before shutdown. Signed-off-by: Guohua Zhong &

[PATCH] HID: i2c-hid: set power sleep before shutdown

f We touch the touchscreen or some other i2c hid device ,the power consumtion will be go up even when the device is in shutdown state. Though the root cause maybe a HW issue. But it seems that it is a good pratice to set power sleep for i2c-hid device before shutdown. Signed-off-by: Guohua Z