[PATCH 00/31] use kmemdup rather than duplicating its implementation
From: Andrzej Hajda
Date: Fri Aug 07 2015 - 04:00:22 EST
Hi,
This patchset was created using fixed version of memdup.cocci
semantic patch [1]. It was compile tested only.
It is based on latest linux-next.
[1]: http://permalink.gmane.org/gmane.linux.kernel/2014320
Regards
Andrzej
Andrzej Hajda (31):
arch/arm/mach-lpc32xx: use kmemdup rather than duplicating its
implementation
arch/ia64/tioce: use kmemdup rather than duplicating its
implementation
arch/m68k/bootinfo: use kmemdup rather than duplicating its
implementation
arch/mips/bcm47xx: use kmemdup rather than duplicating its
implementation
arch/powerpc/nvram: use kmemdup rather than duplicating its
implementation
arch/powerpc/pseries: use kmemdup rather than duplicating its
implementation
arch/x86/microcode: use kmemdup rather than duplicating its
implementation
arch/x86/intel-mid: use kmemdup rather than duplicating its
implementation
crypto: use kmemdup rather than duplicating its implementation
clk/mmp: use kmemdup rather than duplicating its implementation
cpufreq/sfi: use kmemdup rather than duplicating its implementation
drm/amdgpu: use kmemdup rather than duplicating its implementation
memstick: use kmemdup rather than duplicating its implementation
message/fusion: use kmemdup rather than duplicating its implementation
misc/vmw_vmci: use kmemdup rather than duplicating its implementation
net/cavium/liquidio: use kmemdup rather than duplicating its
implementation
scsi/aacraid: use kmemdup rather than duplicating its implementation
scsi/aic7xxx: use kmemdup rather than duplicating its implementation
staging/lustre: use kmemdup rather than duplicating its implementation
fs/cifs: use kmemdup rather than duplicating its implementation
fs/dlm: use kmemdup rather than duplicating its implementation
fs/ntfs: use kmemdup rather than duplicating its implementation
fs/ocfs2: use kmemdup rather than duplicating its implementation
fs/omfs: use kmemdup rather than duplicating its implementation
fs/ubifs: use kmemdup rather than duplicating its implementation
net/sched: use kmemdup rather than duplicating its implementation
net/tipc: use kmemdup rather than duplicating its implementation
net/xfrm: use kmemdup rather than duplicating its implementation
sound/oxfw: use kmemdup rather than duplicating its implementation
sound/atom: use kmemdup rather than duplicating its implementation
sound/soc: use kmemdup rather than duplicating its implementation
arch/arm/mach-lpc32xx/pm.c | 7 ++-----
arch/ia64/sn/pci/tioce_provider.c | 4 ++--
arch/m68k/kernel/bootinfo_proc.c | 4 +---
arch/mips/bcm47xx/buttons.c | 3 +--
arch/powerpc/kernel/nvram_64.c | 3 +--
arch/powerpc/platforms/pseries/hotplug-memory.c | 3 +--
arch/x86/kernel/cpu/microcode/amd.c | 4 +---
arch/x86/kernel/cpu/microcode/intel_early.c | 4 +---
arch/x86/platform/intel-mid/sfi.c | 3 +--
crypto/echainiv.c | 7 ++-----
crypto/seqiv.c | 6 ++----
drivers/clk/mmp/clk-mix.c | 7 +++----
drivers/cpufreq/sfi-cpufreq.c | 4 +---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 4 +---
drivers/memstick/core/mspro_block.c | 3 +--
drivers/message/fusion/mptbase.c | 3 +--
drivers/misc/vmw_vmci/vmci_datagram.c | 3 +--
drivers/net/ethernet/cavium/liquidio/octeon_device.c | 4 +---
drivers/scsi/aacraid/commctrl.c | 7 +++----
drivers/scsi/aic7xxx/aic79xx_core.c | 4 ++--
drivers/scsi/aic7xxx/aic7xxx_core.c | 4 ++--
drivers/staging/lustre/lustre/obdclass/acl.c | 6 ++----
fs/cifs/smb2pdu.c | 5 ++---
fs/dlm/lowcomms.c | 3 +--
fs/ntfs/dir.c | 7 +++----
fs/ocfs2/localalloc.c | 6 ++----
fs/omfs/inode.c | 3 +--
fs/ubifs/lpt.c | 6 ++----
fs/ubifs/tnc.c | 3 +--
net/sched/act_bpf.c | 4 +---
net/sched/cls_bpf.c | 4 +---
net/tipc/server.c | 3 +--
net/xfrm/xfrm_user.c | 6 ++----
sound/firewire/oxfw/oxfw-stream.c | 9 +++------
sound/soc/intel/atom/sst/sst_ipc.c | 3 +--
sound/soc/soc-topology.c | 6 +++---
36 files changed, 57 insertions(+), 108 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/