- 02 Mar, 2016 40 commits
-
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
Amitoj Kaur Chawla <amitoj1606@gmail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Oleg Drokin authored
As it is ENABLE_PINGER is never defined, but in reality it's the code that is now compiled out that should be used since all other instances were converted like that too. Signed-off-by:
Oleg Drokin <green@linuxhacker.ru> Signed-off-by:
-
Oleg Drokin authored
Since there's only one call in those if () else branches, the braces are not really necessary. Highlighted by checkpatch. Signed-off-by:
-
Oleg Drokin authored
KMALLOC_MAX_SIZE is always defined in the kernel, so no point in checking for it, just use t directly. Signed-off-by:
-
Oleg Drokin authored
Found with checkpatch. Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
Signed-off-by:
-
Oleg Drokin authored
Not used in the kernel proper. Signed-off-by:
-
Oleg Drokin authored
Signed-off-by:
-
Oleg Drokin authored
Remove the ifdefs for the around usage. Signed-off-by:
-
Oleg Drokin authored
The new DNE code does not use them either so they are not longer needed. Signed-off-by:
-
Oleg Drokin authored
Since liblustre is no longer with us, referencing to it in the explanations only makes things less clear Signed-off-by:
-
Oleg Drokin authored
These two comments certainly refer to some ifdefed code that is no longer present, so remove them too. Signed-off-by:
-
Oleg Drokin authored
The only caller was not looking at the return value, and liblustre, that cared about it is not part of the kernel client. Signed-off-by:
-
Oleg Drokin authored
And also struct lustre_rw_params that is only referenced by it. Signed-off-by:
-
Oleg Drokin authored
liblustre_check_services is no longer present in the tree. Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" and "space prohibited between function name and open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Randy Dunlap authored
Fix build errors by limiting UNISYS_VISORINPUT to the INPUT kconfig setting. drivers/built-in.o: In function `visorinput_remove': visorinput.c:(.text+0x20802e): undefined reference to `input_unregister_device' drivers/built-in.o: In function `visorinput_probe': visorinput.c:(.text+0x208177): undefined reference to `input_allocate_device' visorinput.c:(.text+0x208241): undefined reference to `input_register_device' visorinput.c:(.text+0x20824d): undefined reference to `input_free_device' visorinput.c:(.text+0x208286): undefined reference to `input_allocate_device' visorinput.c:(.text+0x208302): undefined reference to `input_set_abs_params' visorinput.c:(.text+0x20831a): undefined reference to `input_set_abs_params' visorinput.c:(.text+0x20833f): undefined reference to `input_register_device' visorinput.c:(.text+0x20834b): undefined reference to `input_free_device' visorinput.c:(.text+0x20835f): undefined reference to `input_set_capability' drivers/built-in.o: In function `visorinput_channel_interrupt': visorinput.c:(.text+0x20851e): undefined reference to `input_event' visorinput.c:(.text+0x20862c): undefined reference to `input_event' drivers/built-in.o: In function `input_report_key': visorinput.c:(.text+0x207fd1): undefined reference to `input_event' drivers/built-in.o: In function `input_sync': visorinput.c:(.text+0x207fdc): undefined reference to `input_event' Signed-off-by:
Randy Dunlap <rdunlap@infradead.org> Signed-off-by:
-
Tim Sell authored
This patch saves off the create_bus and create_device controlvm messages for the visorhba device, so that they can be resurrected and used in the kdump kernel. After this patch, a crash dump can be generated using: # service kdump start # echo 1 > /proc/sys/kernel/sysrq # echo c > /proc/sysrq-trigger Signed-off-by:Timothy Sell <timothy.sell@unisys.com> Signed-off-by:
David Kershner <david.kershner@unisys.com> Signed-off-by:
-
Tim Sell authored
Use the dynamic size of the controlvm channel (struct channel_header.size) instead of the statically computed sizeof(struct controlvm_channel) when determining the valid bounds for visorchannel_read() and visorchannel_write(). This prevents an observed problem where kdump was failing because controlvm_channel.local_crash_msg_offset was pointing beyond the statically computed size of the channel, even though the channel was physically large enough. This was causing visorchannel_read() to unecessarily fail, because we thought we were attempting to access memory outside of the channel. Signed-off-by:
-
Tim Sell authored
Previously if controlvm message payloads (indicated in controlvm message via struct controlvm_message.hdr.payload_vm_offset) were contained within the bounds of the channel memory, we would fail to process any controlvm message that contained payload data. Reason is, the request_mem_region() would fail, because it overlapped the channel memory. Since request_mem_region() doesn't actually serve a functional purpose anyway, this was simply removed. Signed-off-by:
-
David Kershner authored
Benjamin Romer is no longer a maintainer for the s-Par drivers. David Kershner will now be the maintainer. Signed-off-by:
Benjamin Romer <benjamin.romer@unisys.com> Signed-off-by:
-
Amitoj Kaur Chawla authored
With concurrency managed workqueues, use of dedicated workqueues can be replaced by using system_wq. Drop visornic_timeout_reset_workqueue by using system_wq. Since there is only one work item per devdata and different devdatas do not need to be ordered, increase of concurrency level by switching to system_wq should not break anything. cancel_work_sync() is used to ensure that work is not pending or executing on any CPU. Signed-off-by:
Tejun Heo <tj@kernel.org> Tested-by:
-
Amitoj Kaur Chawla authored
With concurrency managed workqueues, use of dedicated workqueues can be replaced by using system_wq. Drop periodic_controlvm_workqueue by using system_wq. Since there is only one work item periodic_controlvm_work and different periodic_controlvm_works do not need to be ordered, increase of concurrency level by switching to system_wq should not break anything. cancel_delayed_work_sync() is used to ensure that work is not pending or executing on any CPU. Signed-off-by:
-
Greg Kroah-Hartman authored
Merge tag 'iio-for-4.6c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next Jonathan writes: Third set of IIO new device support, features and cleanups for the 4.6 cycle. Good to see several new contributors in this set - and more generally a number of new 'faces' over this whole cycle. Staging movements * hmc5843 - out of staging. * periodic RTC trigger - driver dropped. This is an ancient driver (brings back some memories ;) that was always somewhat of a bodge. Originally there was a driver that never went into mainline that supported large numbers of periodict timers on the PXA270 via this route. Discussions to have a generic periodic timer subsystem never went anywhere. At the time RTC periodic interrupts were real - now they are emulated using high resolution timers so with the HRT driver this has become pointless. New device support * mpu6050 driver - Add support for the mpu6500. * TI tpl0102 potentiometer - new driver. * Vybrid SoC DAC - new driver. The ADC on this SoC has been supported for a while, this adds a separate driver for the DAC. New Features * hmc5844 - Attributes to configure the bias current (typically part of a self test) This could be done before via a somewhat obscure custom interface. This at least makes it easy to tell what is going on. - Document all custom attributes. * mpu6050 - Add support for calibration offset control and readback. * ms5611 - power regulator support. This is always one that gets added the first time someone has a board that needs it. Here it was needed, hence it was added. Cleanups / minor fixes * tree wide - clean up all the myriad different return values in response to a failure of i2c_check_functionality. After discussions everyone seemed happy wiht -EOPNOTSUPP which seems to describe the situation well. I encouraged a tree wide cleanup to set a good example in future for this. * core - Typos in the iio_event_spec documentation in iio.h * afe4403 - select REGMAP_SPI to avoid dependency issues - mark suspend/resume as __maybe_unused to avoid warnings * afe4404 - mark suspend/resume as __maybe_unused to avoid warnings * atlas-ph-sensor - switch the regmap cache type from linear to rbtree to gain reading of registers on initial startup. It's not immediately obvious, but regmap flat is meant for high performances cases so doesn't read these registers. - use regmap_bulk_read in one case where it was using i2c_smbus_read_i2c_block_data directly (unlike everything else that was through regmap). * ina2xx - stype cleanups (lots of them!) * isl29018 - Get the struct device back from regmap rather than storing another copy of it in the private data. This cleanup makes sense in a number of other drivers so patches may well follow. * mpu6050 - style cleanups (lots of them!) - improved return value handling - use usleep_range to avoid the usual issues with very short msleeps. - add some missing documentation. * ms5611 - use the probed device name for the device rather than the driver name. - select IIO_BUFFER to avoid dependency issues * palmas - drop IRQF_EARLY_RESUME as no longer needed after genirq changes.
-
Greg Kroah-Hartman authored
We want the staging fixes in here as well. Signed-off-by:
-
