debugfs_remove has taken the IS_ERR_OR_NULL into account. Just
remove the unnecessary condition.
Signed-off-by: zhong jiang
---
drivers/md/bcache/super.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
index 2d26f9e
The iterator in for_each_cache is never null, therefore, remove
the redundant null pointer check.
Signed-off-by: zhong jiang
---
drivers/md/bcache/super.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
index
The iterator in for_each_set_bit is never null, therefore, remove
the redundant conditional judgment.
Signed-off-by: zhong jiang
---
drivers/iio/humidity/am2315.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/iio/humidity/am2315.c b/drivers/iio/humidity/am2315.c
ARRAY_SIZE has implemented its function. we prefer to use the function
rather than the open code.
Signed-off-by: zhong jiang
---
drivers/s390/char/vmlogrdr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/s390/char/vmlogrdr.c b/drivers/s390/char/vmlogrdr.c
index
I find the issue with the help of Coccinelle.
zhong jiang (2):
s390: vmlogrdr: Use ARRAY_SIZE instead of reimplementing its function
s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing its
function
drivers/s390/char/vmlogrdr.c | 2 +-
drivers/s390/net/qeth_core_mpc.c | 7
ARRAY_SIZE has implemented its function. we prefer to use the function
rather than the open code.
Signed-off-by: zhong jiang
---
drivers/s390/net/qeth_core_mpc.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/s390/net/qeth_core_mpc.c b/drivers/s390/net
On 2018/9/8 18:21, Thomas Gleixner wrote:
> On Sat, 8 Sep 2018, zhong jiang wrote:
>
>> On 2018/9/8 17:46, Thomas Gleixner wrote:
>>> On Sat, 8 Sep 2018, zhong jiang wrote:
>>>> Hi, Thomas
>>>>
>>>> Can you pick up the patch?
>>>
On 2018/9/8 17:46, Thomas Gleixner wrote:
> On Sat, 8 Sep 2018, zhong jiang wrote:
>> Hi, Thomas
>>
>> Can you pick up the patch?
> I'm not picking up patches for lib/sg_pool. Why would I?
>
I am sorry for that. I regard you as maintainer for lib/sg_pool mist
mempool_destroy has taken null pointer check into account. so remove the
redundant check.
Signed-off-by: zhong jiang
---
drivers/s390/scsi/zfcp_aux.c | 21 +++--
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/drivers/s390/scsi/zfcp_aux.c b/drivers/s390/scsi
Hi, Thomas
Can you pick up the patch?
Thanks
zhong jiang
On 2018/8/1 0:21, zhong jiang wrote:
> kmem_cache_destroy/mempool_destroy has taken null check into account.
> so remove the redundant check.
>
> Signed-off-by: zhong jiang
> ---
> lib/sg_pool.c | 7 +++
&g
kmemdup has implemented the function that kmalloc() + memcpy() will
do. and we prefer to use the kmemdup rather than the open coded implementation.
Signed-off-by: zhong jiang
---
drivers/s390/crypto/zcrypt_msgtype6.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a
kmemdup has implemented the function that kzalloc() + memcpy() will
do. and we prefer to use the kmemdup rather than the open coded implementation.
Signed-off-by: zhong jiang
---
sound/soc/qcom/qdsp6/q6core.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/sound/soc
I find the issue with the help of Coccinelle.
zhong jiang (2):
sound: q6core: Use kmemdup to replace kzalloc + memcpy
sound: skl-topology: Use kmemdup to replace kzalloc + memcpy
sound/soc/intel/skylake/skl-topology.c | 3 +--
sound/soc/qcom/qdsp6/q6core.c | 8 ++--
2 files
kmemdup has implemented the function that kzalloc() + memcpy() will
do. and we prefer to kmemdup rather than the open coded implementation.
Signed-off-by: zhong jiang
---
sound/soc/intel/skylake/skl-topology.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sound/soc/intel
+to maintainers
On 2018/8/18 18:49, zhong jiang wrote:
> debugfs_remove has taken null pointer into account. So it is safe
> to remove the check before debugfs_remove.
>
> Signed-off-by: zhong jiang
> ---
> drivers/acpi/custom_method.c | 3 +--
> 1 file changed, 1 inse
ned-off-by: zhong jiang
---
v1->v2: According to Daniel's suggestion. I modify the subject and commit log.
drivers/thermal/tegra/soctherm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/thermal/tegra/soctherm.c b/drivers/thermal/tegra/soctherm.c
index ed28110..3aa55c9 100644
---
On 2018/8/23 20:19, Alexandre Belloni wrote:
> On 23/08/2018 19:44:38+0800, zhong jiang wrote:
>> Hi, alexandre
>>
>> Can you pick up the patch? Thanks
>>
> We are still in the merge window, this has to wait for v4.19-rc1.
Fine. Thank you for let me know .
Hi, alexandre
Can you pick up the patch? Thanks
Best wishes,
zhong jiang
On 2018/8/16 18:26, zhong jiang wrote:
> of_find_device_by_node takes a reference to the struct device when it
> finds a match via get_device. but it fails to put_device in
> at91_pm_
On 2018/8/13 22:20, don.br...@microchip.com wrote:
>> -Original Message-
>> From: zhong jiang [mailto:zhongji...@huawei.com]
>> Sent: Monday, August 13, 2018 7:43 AM
>> To: don.br...@microsemi.com; j...@linux.vnet.ibm.com;
>> martin.peter...@oracle.com
>&
Ping , Anyone has any objection with the patchset ?
Thanks,
zhong jiang
On 2018/8/16 23:58, zhong jiang wrote:
> The issue is detected with the help of Coccinelle.
>
> v1->v2:
> - According to Florian's suggestion, change the subject of the patch.
>
> zhong jiang (2):
turn;
>
> - eFuseWord = (u16 **)rtw_malloc2d(EFUSE_MAX_SECTION_88E,
> EFUSE_MAX_WORD_UNIT, sizeof(u16));
> + eFuseWord = (u16 **)rtw_malloc2d(EFUSE_MAX_SECTION_88E,
> + EFUSE_MAX_WORD_UNIT, (int)sizeof(u16));
>
You should be align with left parenthesis.
Thanks,
On 2018/8/18 22:01, Julia Lawall wrote:
>
> On Sat, 18 Aug 2018, zhong jiang wrote:
>
>> On 2018/8/18 20:52, Himanshu Jha wrote:
>>> On Sat, Aug 18, 2018 at 08:01:40PM +0800, zhong jiang wrote:
>>>> Because pci_alloc_consistent has been deprecated. We prefer to
Because pci_alloc_consistent has been deprecated. We prefer to use
dma_alloc_coherent directly. Therefore, we should remove pci_alloc_consistent
to increase the confidence.
Acked-by: Julia Lawall
Acked-by: Himanshu Jha
Signed-off-by: zhong jiang
---
v1->v2:
- fix some spelling mista
On 2018/8/18 20:52, Himanshu Jha wrote:
> On Sat, Aug 18, 2018 at 08:01:40PM +0800, zhong jiang wrote:
>> Because pci_alloc_consistent has been deprecated. We prefer to use
>> dam_alloc_coherent directly. Therefore, we should remove pci_alloc_consistent
> ^^^ typo "dma
Because pci_alloc_consistent has been deprecated. We prefer to use
dam_alloc_coherent directly. Therefore, we should remove pci_alloc_consistent
to increase the confidence.
Signed-off-by: zhong jiang
---
scripts/coccinelle/api/alloc/zalloc-simple.cocci | 41 +---
1 file
We prefer to ERR_CAST rather than ERR_PTR(PTR_ERR()), So just
replace it.
The issue is detected with the help of Coccinelle
Signed-off-by: zhong jiang
---
drivers/gpu/drm/omapdrm/dss/dss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/omapdrm/dss/dss.c
b
debugfs_remove has taken null pointer into account. So it is safe
to remove the check before debugfs_remove.
Signed-off-by: zhong jiang
---
drivers/acpi/custom_method.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/acpi/custom_method.c b/drivers/acpi
We should use NULL to compare with pointer-typed value rather than
0. The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
drivers/ide/pmac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ide/pmac.c b/drivers/ide/pmac.c
index c5b902b
On 2018/8/17 21:23, zhong jiang wrote:
> We should use NULL to compare with pointer-typed value rather than
> 0. The issue is detected with the help of Coccinelle.
>
> Signed-off-by: zhong jiang
> ---
> drivers/ide/pmac.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletio
We should use NULL to compare with pointer-typed value rather than
0. The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
drivers/ide/pmac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ide/pmac.c b/drivers/ide/pmac.c
index c5b902b
dma_pool_destroy has taken the null pointer into account. so just
remove the null pointer check.
Signed-off-by: zhong jiang
---
drivers/thunderbolt/ctl.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/thunderbolt/ctl.c b/drivers/thunderbolt/ctl.c
index 37a7f4c
On 2018/8/17 17:18, Laurent Pinchart wrote:
> Hi Zhong,
>
> Thank you for the patch.
>
> On Friday, 17 August 2018 06:37:26 EEST zhong jiang wrote:
>> debugfs_remove_recursive has taken null pointer into account. so
>> remove the unneeded check.
>>
>> Signed-
On 2018/8/17 11:24, zhong jiang wrote:
> kfree has taken null pointer into account. so check the null pointer
> before kfree is meanless.
meanless/meaningless. will repost. please ignore the patch, thanks.
> Signed-off-by: zhong jiang
> ---
> drivers/misc/sgi-xp/xpc_partition
kfree has taken null pointer into account. so check the null pointer
before kfree is meaningless.
Signed-off-by: zhong jiang
---
drivers/misc/sgi-xp/xpc_partition.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/misc/sgi-xp/xpc_partition.c
b/drivers/misc/sgi-xp
subect: drviers/drivers will repost, please ingore the patch. Thanks
On 2018/8/17 11:31, zhong jiang wrote:
> debugfs_remove_recursive has taken the null pointer into account.
> just remove the null check before debugfs_remove_recursive.
>
> Signed-off-by: zhong jiang
> ---
>
debugfs_remove_recursive has taken null pointer into account. so
remove the unneeded check.
Signed-off-by: zhong jiang
---
drivers/media/usb/uvc/uvc_debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/media/usb/uvc/uvc_debugfs.c
b/drivers/media/usb/uvc
debugfs_remove_recursive has taken the null pointer into account.
just remove the null check before debugfs_remove_recursive.
Signed-off-by: zhong jiang
---
drivers/platform/x86/intel_ips.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b
debugfs_remove_recursive has taken the null pointer into account.
just remove the null check before debugfs_remove_recursive.
Signed-off-by: zhong jiang
---
drivers/platform/x86/intel_ips.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b
kfree has taken null pointer into account. so check the null pointer
before kfree is meanless.
Signed-off-by: zhong jiang
---
drivers/misc/sgi-xp/xpc_partition.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/misc/sgi-xp/xpc_partition.c
b/drivers/misc/sgi-xp
On 2018/8/14 14:39, Daniel Lezcano wrote:
> On 09/08/2018 15:40, zhong jiang wrote:
>> Device node iterators will get the return node. Meawhile, It is
>> also put the previous device node. An explicit put will cause
>> a double put.
> What about:
>
> Subject: drive
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/phy/broadcom/phy-brcm-usb.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/broadcom/phy-brcm
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/phy/lantiq/phy-lantiq-rcu-usb2.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/lantiq/phy-lantiq
The issue is detected with the help of Coccinelle.
v1->v2:
- According to Florian's suggestion, change the subject of the patch.
zhong jiang (2):
phy:phy-brcm-usb: Use PTR_ERR_OR_ZERO to replace the open coded
version
phy:phy-lantiq-rcu-usb2: Use PTR_ERR_OR_ZERO to replace
instead of of_node_put in at91_pm_config_ws.
Fixes: d7484f5c6b3b ("ARM: at91: pm: configure wakeup sources for ULP1 mode")
Suggested-by: Claudiu Beznea
Signed-off-by: zhong jiang
---
arch/arm/mach-at91/pm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm
On 2018/8/16 17:32, Claudiu Beznea wrote:
> Hi Alexandre,
>
> On 14.08.2018 15:59, Alexandre Belloni wrote:
>> On 14/08/2018 09:54:56+0800, zhong jiang wrote:
>>> Device node iterators put the previous value of the index variable,
>>> so an explicit put
On 2018/8/16 7:23, Florian Fainelli wrote:
> On 08/13/2018 04:24 AM, zhong jiang wrote:
>> PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
>> just replace them rather than duplicating its implement.
> Subject should be:
>
> phy: phy-brcm-usb: Use PTR_ERR
On 2018/8/15 0:15, Alexandre Belloni wrote:
> Hi,
>
> On 13/08/2018 19:31:24+0800, zhong jiang wrote:
>> PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
>> just replace them rather than duplicating its implement.
>>
>> Signed-off-by: zhong
We prefer to ARRAY_SIZE rather than duplicating its implementation.
And just one place use the #define variable, therefore, remove
PFM_CMD_COUNT definition altogether.
Signed-off-by: zhong jiang
---
v1->v2:
- According to Joe's suggestion. remove the #define variable,
and use AR
On 2018/8/14 14:39, Daniel Lezcano wrote:
> On 09/08/2018 15:40, zhong jiang wrote:
>> Device node iterators will get the return node. Meawhile, It is
>> also put the previous device node. An explicit put will cause
>> a double put.
> What about:
>
> Subject: drive
Device node iterators put the previous value of the index variable,
so an explicit put causes a double put.
I detect the issue with the help of Coccinelle.
Signed-off-by: zhong jiang
---
arch/arm/mach-at91/pm.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/arch/arm
On 2018/8/13 20:28, Vladimir Zapolskiy wrote:
> Hi zhong jiang,
>
> On 08/10/2018 05:40 AM, zhong jiang wrote:
>> kmemdup is better than kmalloc() + memcpy(), and we do not like
>> open code. So just use kmemdup instead.
>>
>> Signed-off-by: zhong jiang
>>
vmemdup_user is better than duplicating its implementation, So just
replace the open code.
The issue is detected with the help of Coccinelle.
Signed-off-by: zhong jiang
---
drivers/scsi/hpsa.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/scsi/hpsa.c
Please ignore the patch, will repost . Thanks
On 2018/8/13 20:22, zhong jiang wrote:
> vmemdup_user is better than duplicating its implementation, So just
> replace the open code.
>
> Signed-off-by: zhong jiang
> ---
> drivers/scsi/hpsa.c | 10 +++---
> 1 file change
vmemdup_user is better than duplicating its implementation, So just
replace the open code.
Signed-off-by: zhong jiang
---
drivers/scsi/hpsa.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 58bb70b..948576a 100644
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/rtc/rtc-digicolor.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/rtc/rtc-digicolor.c b/drivers/rtc
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/rtc/rtc-ds1347.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-ds1347.c b/drivers/rtc/rtc
The issue is detected with the help of Coccinelle.
zhong jiang (2):
rtc:rtc-digicolor: Use PTR_ERR_OR_ZERO to replace the open code
rtc:rtc-ds1347: Use PTR_ERR_OR_ZERO to replace the open code
drivers/rtc/rtc-digicolor.c | 4 +---
drivers/rtc/rtc-ds1347.c| 5 +
2 files changed, 2
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/phy/broadcom/phy-brcm-usb.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/broadcom/phy-brcm
The issue is detected with the help of Coccinelle.
zhong jiang (2):
phy:phy-brcm-us: Use PTR_ERR_OR_ZERO to replace the open code
phy:phy-lantiq-rcu-usb2: Use PTR_ERR_OR_ZERO to replace the open code
drivers/phy/broadcom/phy-brcm-usb.c | 4 +---
drivers/phy/lantiq/phy-lantiq-rcu-usb2.c
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/phy/lantiq/phy-lantiq-rcu-usb2.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/lantiq/phy-lantiq
On 2018/8/13 19:26, Sergio Paracuellos wrote:
> On Mon, Aug 13, 2018 at 12:54 PM, zhong jiang wrote:
>> PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
>> just replace them rather than duplicating its implement.
>>
>> Signed-off-by: zhong jiang
>&g
PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
just replace them rather than duplicating its implement.
Signed-off-by: zhong jiang
---
drivers/staging/mt7621-pci/pci-mt7621.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/staging/mt7621-pci/pci
kmemdup is better than kmalloc() + memcpy(), and we do not like
open code. So just use kmemdup instead.
Signed-off-by: zhong jiang
---
arch/arm/mach-lpc32xx/pm.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-lpc32xx/pm.c b/arch/arm/mach-lpc32xx/pm.c
The kmemdup has implemented the function that kmalloc() + memcpy will
do. So just replace them to make the code concise.
Signed-off-by: zhong jiang
---
arch/ia64/sn/pci/tioce_provider.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/ia64/sn/pci/tioce_provider.c
b
There are some extra semicolon in pmsa-v8.c. So just remove them.
I detect the issue with the help of Coccinelle.
Signed-off-by: zhong jiang
---
arch/arm/mm/pmsa-v8.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mm/pmsa-v8.c b/arch/arm/mm/pmsa-v8.c
index
There are some extra semicolon in arm64 architecture. Just remove them.
zhong jiang (2):
arm64/kprobes: remove an extra semicolon in arch_prepare_kprobe
arm64:guest: remove some extra semicolon in kvm_target_cpu
arch/arm64/kernel/probes/kprobes.c | 2 +-
arch/arm64/kvm/guest.c
There is an extra semicolon in arch_prepare_kprobe, remove it.
Signed-off-by: zhong jiang
---
arch/arm64/kernel/probes/kprobes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/probes/kprobes.c
b/arch/arm64/kernel/probes/kprobes.c
index e78c3ef..9b65132
There are some extra semicolon in kvm_target_cpu, remove it.
Signed-off-by: zhong jiang
---
arch/arm64/kvm/guest.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kvm/guest.c b/arch/arm64/kvm/guest.c
index 07256b0..a74f84d 100644
--- a/arch/arm64/kvm/guest.c
Device node iterators will get the return node. Meawhile, It is
also put the previous device node. An explicit put will cause
a double put.
Signed-off-by: zhong jiang
---
drivers/thermal/tegra/soctherm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/thermal/tegra/soctherm.c b
kmem_cache_destroy has taken null pointer into account. So it is
safe to drop the null check before calling the function.
Signed-off-by: zhong jiang
---
drivers/block/drbd/drbd_main.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/block/drbd/drbd_main.c
mempool_destroy has taken the null pointer into account. So it is safe
to remove the null check.
Signed-off-by: zhong jiang
---
drivers/block/aoe/aoedev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/aoe/aoedev.c b/drivers/block/aoe/aoedev.c
index
debugfs_remove_recursive has taken null pointer into account. So it is
safe to drop the null check before calling the funtion.
Signed-off-by: zhong jiang
---
drivers/block/mtip32xx/mtip32xx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/block/mtip32xx/mtip32xx.c
That semicolons are unneeded, Just remove them.
Signed-off-by: zhong jiang
---
drivers/staging/gasket/gasket_interrupt.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/gasket/gasket_interrupt.c
b/drivers/staging/gasket/gasket_interrupt.c
index 09c3d07
On 2018/8/5 23:27, Joe Perches wrote:
> On Sun, 2018-08-05 at 23:02 +0800, zhong jiang wrote:
>> The err is not used after initalization, So remove it and make
>> the function to be void function.
> []
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> []
>>
On 2018/8/6 3:14, Nikolay Borisov wrote:
>
> On 5.08.2018 18:02, zhong jiang wrote:
>> zhong jiang (3):
>> fs/btrfs/disk-io: Remove unneeded variable "err"
>> fs/btrfs/extent-tree: remove redudant variable "err"
>> fs/btrfs/tree-log: remov
On 2018/8/6 8:33, David Miller wrote:
> From: zhong jiang
> Date: Sun, 5 Aug 2018 22:18:43 +0800
>
>> @@ -1797,7 +1795,7 @@ static int br_multicast_ipv4_rcv(struct net_bridge *br,
>> struct sk_buff *skb_trimmed = NULL;
>> const unsigned char *src;
>>
On 2018/8/6 9:27, Gao Xiang wrote:
> Hi Jiang,
>
> On 2018/8/5 21:57, zhong jiang wrote:
>> That semicolons are unneeded, JUst remove them.
>>
>> Signed-off-by: zhong jiang
> Thanks for your patch. Since erofs and gasket are different feature, it is
> better to
That semicolons are unneeded, JUst remove them.
Signed-off-by: zhong jiang
---
drivers/staging/erofs/unzip_vle.c | 2 +-
drivers/staging/gasket/gasket_interrupt.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/erofs/unzip_vle.c
b/drivers
On 2018/8/3 21:21, Steven Rostedt wrote:
> On Fri, 3 Aug 2018 20:40:02 +0800
> zhong jiang wrote:
>
>> Fix the following warning.
>>
>> kernel/kthread.c:859:6: warning: symbol '__kthread_queue_delayed_work' was
>> not declared. Should it be stat
On 2018/8/5 5:24, Theodore Y. Ts'o wrote:
> On Sat, Aug 04, 2018 at 07:04:56PM +0800, zhong jiang wrote:
>> The err is not used after initalization. So just remove the variable.
>>
>> Signed-off-by: zhong jiang
> I'll apply this patch, but how did you generate t
The err is not used after initalization. So just remove the variable.
Signed-off-by: zhong jiang
---
fs/ext4/mballoc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 8b24d3d..e29fce2 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4
Fix the following warning.
kernel/kthread.c:859:6: warning: symbol '__kthread_queue_delayed_work' was not
declared. Should it be static?
Signed-off-by: zhong jiang
---
kernel/kthread.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/kthread.c b/kernel
Fix the following warning.
kernel/sched/topology.c:10:15: warning: symbol 'sched_domains_tmpmask' was not
declared. Should it be static?
kernel/sched/topology.c:11:15: warning: symbol 'sched_domains_tmpmask2' was not
declared. Should it be static?
Signed-off-by: zhong jian
On 2018/7/22 13:41, zhong jiang wrote:
> Fix the following warning:
>
> drivers/gpu/drm/nouveau/dispnv50/wndw.c:570:1: error: symbol 'nv50_wndw_new_'
> redeclared with different type
> (originally declared at drivers/gpu/drm/nouveau/dispnv50/wndw.h:39) -
> incomp
On 2018/8/2 21:31, Matthew Wilcox wrote:
> On Thu, Aug 02, 2018 at 02:22:03PM +0800, zhong jiang wrote:
>> On 2018/8/1 23:37, Matthew Wilcox wrote:
>>> Please post the code.
>> when module is loaded. we create the specific mempool. The code flow is as
>> follows.
>
Commit-ID: 0b2c1aec49ddb2260894df6c69ae7b34142ff936
Gitweb: https://git.kernel.org/tip/0b2c1aec49ddb2260894df6c69ae7b34142ff936
Author: Zhong Jiang
AuthorDate: Sat, 21 Jul 2018 16:33:24 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 2 Aug 2018 14:33:19 +0200
x86/iommu: Use NULL
Commit-ID: c7ba9f7cb55926605983187a68624999b93abb94
Gitweb: https://git.kernel.org/tip/c7ba9f7cb55926605983187a68624999b93abb94
Author: zhong jiang
AuthorDate: Wed, 1 Aug 2018 00:08:06 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 2 Aug 2018 14:25:40 +0200
x86/platform/olpc: Use
Commit-ID: 3ff4f80a74fd38398ae1bd8a458ba9c51aa0dd44
Gitweb: https://git.kernel.org/tip/3ff4f80a74fd38398ae1bd8a458ba9c51aa0dd44
Author: Zhong Jiang
AuthorDate: Wed, 1 Aug 2018 00:24:58 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 2 Aug 2018 13:53:04 +0200
debugobjects: Remove
4/4] do nothing. just add Andy's review-by.
zhong jiang (4):
driver/scsi/fnic/fnic_trace: Use kvcalloc instead of vmalloc+memset
drivers/scsi/dpt_i2o: Use dma_zalloc_coherent to repalce
dma_alloc_coherent+memset
drivers/scsi/snic/snic_trc: Use kvcalloc instead of vmalloc+memset
drive
The kvcalloc is better than vmalloc() + memset() , So replace them.
Signed-off-by: zhong jiang
---
drivers/scsi/snic/snic_trc.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/snic/snic_trc.c b/drivers/scsi/snic/snic_trc.c
index fc60c93..e766fa2 100644
On 2018/8/1 23:37, Matthew Wilcox wrote:
> On Wed, Aug 01, 2018 at 11:31:15PM +0800, zhong jiang wrote:
>> Hi, Everyone
>>
>> I ran across the following novel case similar to memory leak in linux-4.1
>> stable when allocating
>> memory object by kmem_cache_all
On 2018/8/2 11:04, Al Viro wrote:
> On Thu, Aug 02, 2018 at 10:00:28AM +0800, zhong jiang wrote:
>> dump_align is used to double check in a expression. It is redundant.
>> so just remove one of them.
>
> What makes you think that it is redundant?
>
I am sorry for that.
On 2018/8/2 10:34, Matthew Wilcox wrote:
> On Thu, Aug 02, 2018 at 10:00:28AM +0800, zhong jiang wrote:
>> dump_align is used to double check in a expression. It is redundant.
>> so just remove one of them.
> You're wrong. Functions in C can have side-effects (and this one
plese ingore it.
On 2018/8/2 10:04, zhong jiang wrote:
> It is unncessary to use double test for a expression. so just
> remove one of them.
>
> Signed-off-by: zhong jiang
> ---
> fs/binfmt_elf_fdpic.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-
It is unncessary to use double test for a expression. so just
remove one of them.
Signed-off-by: zhong jiang
---
fs/binfmt_elf_fdpic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c
index b53bb37..5162372 100644
--- a/fs
dump_align is used to double check in a expression. It is redundant.
so just remove one of them.
Signed-off-by: zhong jiang
---
fs/binfmt_elf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index efae2fb..b6c5b02 100644
--- a/fs
gister the moudle.
but I check the code(mm/slub.c) carefully . I can not find any clue to prove my
assumption.
I will be appreciate if anyone have any idea about the case.
Thanks
zhong jiang
we prefer to use dma_zalloc_coherent rather than dam_alloc_coherent+memset
Signed-off-by: zhong jiang
---
drivers/staging/mt7621-eth/mtk_eth_soc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/mt7621-eth/mtk_eth_soc.c
b/drivers/staging/mt7621-eth
we prefer to the kmemdup rather than kmalloc+memcpy. so just
replace them.
Signed-off-by: zhong jiang
---
kernel/module.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/kernel/module.c b/kernel/module.c
index 20344e4..6746c85 100644
--- a/kernel/module.c
+++ b/kernel
kmem_cache_destroy has taken the null check into account. so just
remove the unnecessary check.
Signed-off-by: zhong jiang
---
lib/debugobjects.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/debugobjects.c b/lib/debugobjects.c
index 994be48..7a6d80b 100644
--- a/lib
201 - 300 of 437 matches
Mail list logo