[PATCH] greybus: gpio: switch GPIO portions to use GPIOLIB_IRQCHIP

2018-11-08 Thread Nishad Kamdar
Convert the GPIO driver to use the GPIO irqchip library GPIOLIB_IRQCHIP instead of reimplementing the same. Signed-off-by: Nishad Kamdar --- drivers/staging/greybus/Kconfig | 1 + drivers/staging/greybus/gpio.c | 123 ++-- 2 files changed, 21 insertions(+), 103

[PATCH v3 4/4] staging: iio: ad7816: Add device tree table.

2018-11-08 Thread Nishad Kamdar
Add device tree table for matching vendor ID. Signed-off-by: Nishad Kamdar --- drivers/staging/iio/adc/ad7816.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/staging/iio/adc/ad7816.c b/drivers/staging/iio/adc/ad7816.c index a2fead85cd46..b8a9149fbac1 100644 ---

[PATCH v3 3/4] staging: iio: ad7816: Set RD/WR pin and CONVST pin as outputs.

2018-11-08 Thread Nishad Kamdar
The RD/WR pin and CONVST pin are logical inputs to the AD78xx chip as per the datasheet. Hence convert them to outputs. Signed-off-by: Nishad Kamdar --- drivers/staging/iio/adc/ad7816.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/staging/iio/adc/ad7816.c

[PATCH v3 2/4] staging: iio: ad7816: Do not use busy_pin in case of AD7818

2018-11-08 Thread Nishad Kamdar
AD7818 does not support busy_pin functionality as per datasheet. Hence drop busy_pin when AD7818 is used. Signed-off-by: Nishad Kamdar --- drivers/staging/iio/adc/ad7816.c | 35 ++-- 1 file changed, 24 insertions(+), 11 deletions(-) diff --git

[PATCH v3 1/4] staging: iio: ad7816: Switch to the gpio descriptor interface

2018-11-08 Thread Nishad Kamdar
Use the gpiod interface for rdwr_pin, convert_pin and busy_pin instead of the deprecated old non-descriptor interface. Signed-off-by: Nishad Kamdar --- drivers/staging/iio/adc/ad7816.c | 80 ++-- 1 file changed, 34 insertions(+), 46 deletions(-) diff --git

[PATCH v3 0/4] staging: iio: ad7816: Switch to the gpio descriptor interface

2018-11-08 Thread Nishad Kamdar
Changes in v4: - Drop busy pin in case of AD7818. - Set RD/WR pin and CONVST pin as outputs. - Add device tree table. Nishad Kamdar (4): staging: iio: ad7816: Switch to the gpio descriptor interface staging: iio: ad7816: Do not use busy_pin in case of AD7818 staging: iio: ad7816: Set

Re: [PATCH v2] staging: wilc1000: update wilc1000 driver maintainer ids

2018-11-08 Thread Ganesh.Krishna
From: Ajay Singh We would like to update the maintainer email id's for wilc1000 driver. Signed-off-by: Aditya Shankar Signed-off-by: Ganesh Krishna Signed-off-by: Adham Abozaeid Signed-off-by: Ajay Singh Acked-by: Ganesh Krishna --- Changes in

[PATCH] staging: rtl8723bs: Add missing return for cfg80211_rtw_get_station

2018-11-08 Thread Larry Finger
With Androidx86 8.1, wificond returns "failed to get nl80211_sta_info_tx_failed" and wificondControl returns "Invalid signal poll result from wificond". The fix is to OR sinfo->filled with BIT_ULL(NL80211_STA_INFO_TX_FAILED). This missing bit is apparently not needed with NetworkManager, but it

[PATCH] drivers/android/binder.c: Remove duplicate header

2018-11-08 Thread Brajeswar Ghosh
Remove binder_trace.h which is included more than once Signed-off-by: Brajeswar Ghosh --- drivers/android/binder.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/android/binder.c b/drivers/android/binder.c index cb30a524d16d..719f35a5c04b 100644 --- a/drivers/android/binder.c +++

Re: [PATCH v4 1/3] staging: wilc1000: validate cfg parameters before scheduling the work

2018-11-08 Thread Greg KH
On Thu, Nov 08, 2018 at 09:50:25PM +, adham.aboza...@microchip.com wrote: > From: Adham Abozaeid > > From: Adham Abozaeid Twice? Something went wrong on your side, for all of these patches :( Please fix up and resend. thanks, greg k-h ___

[PATCH v4 1/3] staging: wilc1000: validate cfg parameters before scheduling the work

2018-11-08 Thread Adham.Abozaeid
From: Adham Abozaeid From: Adham Abozaeid Validate cfg parameters after being called by cfg80211 in set_wiphy_params before scheduling the work executed in handle_cfg_param Signed-off-by: Adham Abozaeid --- drivers/staging/wilc1000/host_interface.c | 61 ++-

[PATCH v4 0/3] staging: wilc1000: validate input to set_wiphy_param and return proper

2018-11-08 Thread Adham.Abozaeid
From: Adham Abozaeid Validate input parameters to set_wiphy_param before scheduling handle_cfg_param() to validate them. This way proper errors can be returned to caller. Also cleaned up unused code in handle_cfg_param. Changes since v1: - Correction spelling in subject of patch#2 - Added From:

[PATCH v4 3/3] staging: wilc1000: Remove unused mutex cfg_values_lock

2018-11-08 Thread Adham.Abozaeid
From: Adham Abozaeid From: Adham Abozaeid After removing cfg_values member, cfg_values_lock that was used to protect it can also be removed. Signed-off-by: Adham Abozaeid --- drivers/staging/wilc1000/host_interface.c | 9 - drivers/staging/wilc1000/host_interface.h | 2 -- 2 files

[PATCH v4 2/3] staging: wilc1000: Don't keep a copy of wiphy parameters in the driver

2018-11-08 Thread Adham.Abozaeid
From: Adham Abozaeid From: Adham Abozaeid host_if_drv.cfg_values is a write only member, and can be removed Signed-off-by: Adham Abozaeid --- drivers/staging/wilc1000/host_interface.c | 13 - drivers/staging/wilc1000/host_interface.h | 1 - 2 files changed, 14 deletions(-)

Re: [PATCH] Add carve out heap name initialization

2018-11-08 Thread Alexey Skidanov
On 11/8/18 9:41 PM, Laura Abbott wrote: > On 11/8/18 11:34 AM, Alexey Skidanov wrote: >> >> >> On 11/8/18 9:15 PM, Laura Abbott wrote: >>> On 10/22/18 2:15 PM, Alexey Skidanov wrote: Heap name is mundatory. >>> >>> I'm wary of this and the other change because it misses the >>> broader

Re: [PATCH] Add carve out heap name initialization

2018-11-08 Thread Laura Abbott
On 11/8/18 11:34 AM, Alexey Skidanov wrote: On 11/8/18 9:15 PM, Laura Abbott wrote: On 10/22/18 2:15 PM, Alexey Skidanov wrote: Heap name is mundatory. I'm wary of this and the other change because it misses the broader problem of dealing with the carveout heaps. I still want to remove

Re: [PATCH] Add carve out heap name initialization

2018-11-08 Thread Alexey Skidanov
On 11/8/18 9:15 PM, Laura Abbott wrote: > On 10/22/18 2:15 PM, Alexey Skidanov wrote: >> Heap name is mundatory. >> > > I'm wary of this and the other change because it misses the > broader problem of dealing with the carveout heaps. > I still want to remove the carveout and chunk heap. I get >

Re: [PATCH] Add carve out heap name initialization

2018-11-08 Thread Laura Abbott
On 10/22/18 2:15 PM, Alexey Skidanov wrote: Heap name is mundatory. I'm wary of this and the other change because it misses the broader problem of dealing with the carveout heaps. I still want to remove the carveout and chunk heap. I get that it's being used for out of tree work but at this

Re: [PATCH v5] staging: android: ion: Add per-heap counters

2018-11-08 Thread Laura Abbott
On 10/9/18 12:08 PM, Alexey Skidanov wrote: Heap statistics have been removed and currently even basics statistics are missing. This patch creates per heap debugfs directory /sys/kernel/debug/ and adds the following counters: - the number of allocated buffers; - the number of allocated bytes; -

Re: [PATCH v2 1/2] staging: iio: ad7780: check if ad778x before gain update

2018-11-08 Thread Tomasz Duszynski
Hi Giuliano, Comment inline. On 11/8/18 2:03 PM, Giuliano Belinassi wrote: > Only the ad778x have the 'gain' status bit. Check it before updating > through a new variable is_ad778x in chip_info. > > Signed-off-by: Giuliano Belinassi > --- > Changes in v2: > - Squashed is_ad778x

Re: [PATCH v3 2/4] staging: wilc1000: validate cfg parameters before scheduling the work

2018-11-08 Thread Adham.Abozaeid
On 11/8/18 4:22 AM, Greg KH wrote: > On Tue, Nov 06, 2018 at 12:01:18AM +, adham.aboza...@microchip.com wrote: >> From: Adham Abozaeid >> >> Validate cfg parameters after being called by cfg80211 in set_wiphy_params >> before scheduling the work executed in handle_cfg_param >> >>

[Resend PATCH V5 2/10] x86/hyper-v: Add HvFlushGuestAddressList hypercall support

2018-11-08 Thread lantianyu1986
From: Lan Tianyu Hyper-V provides HvFlushGuestAddressList() hypercall to flush EPT tlb with specified ranges. This patch is to add the hypercall support. Reviewed-by: Michael Kelley Signed-off-by: Lan Tianyu --- Change sincd v4: - Expose function hyperv_fill_flush_guest_mapping_list()

[Resend PATCH V5 3/10] x86/Hyper-v: Add trace in the hyperv_nested_flush_guest_mapping_range()

2018-11-08 Thread lantianyu1986
From: Lan Tianyu This patch is to trace log in the hyperv_nested_flush_ guest_mapping_range(). Signed-off-by: Lan Tianyu --- arch/x86/hyperv/nested.c| 1 + arch/x86/include/asm/trace/hyperv.h | 14 ++ 2 files changed, 15 insertions(+) diff --git

[Resend PATCH V5 1/10] KVM: Add tlb_remote_flush_with_range callback in kvm_x86_ops

2018-11-08 Thread lantianyu1986
From: Lan Tianyu Add flush range call back in the kvm_x86_ops and platform can use it to register its associated function. The parameter "kvm_tlb_range" accepts a single range and flush list which contains a list of ranges. Signed-off-by: Lan Tianyu --- Change since v1: Change "end_gfn"

[PATCH V5 00/10] x86/KVM/Hyper-v: Add HV ept tlb range flush hypercall support in KVM

2018-11-08 Thread lantianyu1986
From: Lan Tianyu Sorry. Some patches was blocked and I try to resend via another account. For nested memory virtualization, Hyper-v doesn't set write-protect L1 hypervisor EPT page directory and page table node to track changes while it relies on guest to tell it changes via

Re: [PATCH V3] binder: ipc namespace support for android binder

2018-11-08 Thread Christian Brauner
On Thu, Nov 08, 2018 at 01:02:32PM +, chouryzhou(周威) wrote: > We are working for running android in container, but we found that binder is > not isolated by ipc namespace. Since binder is a form of IPC and therefore > should > be tied to ipc namespace. With this patch, we can run more than

Re: [PATCH v2 2/2] staging: iio: ad7780: generates pattern_mask from PAT bits

2018-11-08 Thread Ardelean, Alexandru
On Thu, 2018-11-08 at 11:03 -0200, Giuliano Belinassi wrote: > Previously, all pattern_masks and patterns in the chip_info table were > hardcoded. Now they are generated using the PAT macros, as described in > the datasheets. One comment about indentation/whitespace. Rest looks good. Alex > >

Re: [PATCH v2 1/2] staging: iio: ad7780: check if ad778x before gain update

2018-11-08 Thread Ardelean, Alexandru
On Thu, 2018-11-08 at 11:03 -0200, Giuliano Belinassi wrote: > Only the ad778x have the 'gain' status bit. Check it before updating > through a new variable is_ad778x in chip_info. > Looks good. Alex > Signed-off-by: Giuliano Belinassi > --- > Changes in v2: > - Squashed is_ad778x

[PATCH v2 2/2] staging: iio: ad7780: generates pattern_mask from PAT bits

2018-11-08 Thread Giuliano Belinassi
Previously, all pattern_masks and patterns in the chip_info table were hardcoded. Now they are generated using the PAT macros, as described in the datasheets. Signed-off-by: Giuliano Belinassi --- Changes in v2: - Added the PATTERN and PATTERN_MASK macros - Update BIT macros

[PATCH v2 1/2] staging: iio: ad7780: check if ad778x before gain update

2018-11-08 Thread Giuliano Belinassi
Only the ad778x have the 'gain' status bit. Check it before updating through a new variable is_ad778x in chip_info. Signed-off-by: Giuliano Belinassi --- Changes in v2: - Squashed is_ad778x declaration commit with the ad778x checkage - Changed is_ad778x type to bool

[PATCH v2 0/2] pattern generation and gain update

2018-11-08 Thread Giuliano Belinassi
This series of patches fixes a bug in ad717x chips where the PAT2 bit was wrongly read as a GAIN bit. It also refactors the pattern_mask generation with the PAT bits. Changelog: * v2 - Squashed is_add778x flag commit with the gain update fix - Changed u8 is_add778x to bool

[PATCH V3] binder: ipc namespace support for android binder

2018-11-08 Thread 周威
We are working for running android in container, but we found that binder is not isolated by ipc namespace. Since binder is a form of IPC and therefore should be tied to ipc namespace. With this patch, we can run more than one android container on one host. This patch move "binder_procs" and

HELLO! DEAR! GOOD NEWS TO YOU

2018-11-08 Thread Mr Jay Clayton
Dear customer, This is to inform you that we have been mandated by the APEX BANK to delivery all outstanding unclaimed compensation/inheritance funds to the rightful owners with immediate effect. Your ATM Card of $3.7 million USD has been approved This is in collaboration with

Re: [PATCH] media: staging: tegra-vde: print long unsigned using %lu format specifier

2018-11-08 Thread Dmitry Osipenko
On 08.11.2018 14:02, Colin King wrote: > From: Colin Ian King > > The frame.flags & FLAG_B_FRAME is promoted to a long unsigned because > of the use of the BIT() macro when defining FLAG_B_FRAME and causing a > build warning. Fix this by using the %lu format specifer. > > Cleans up warning: >

Re: [PATCH 2/3] staging: wlan-ng: reformatting in hfa384x.h to fit 80 character limit

2018-11-08 Thread Greg KH
On Wed, Nov 07, 2018 at 08:09:19PM +, Tim Collier wrote: > Reformat lines over 80 characters in hfa384x.h to resolve "line over > 80 characters" warnings reported by checkpatch. > > Signed-off-by: Tim Collier > --- > drivers/staging/wlan-ng/hfa384x.h | 26 ++ > 1

Re: [PATCH v3 2/4] staging: wilc1000: validate cfg parameters before scheduling the work

2018-11-08 Thread Greg KH
On Tue, Nov 06, 2018 at 12:01:18AM +, adham.aboza...@microchip.com wrote: > From: Adham Abozaeid > > Validate cfg parameters after being called by cfg80211 in set_wiphy_params > before scheduling the work executed in handle_cfg_param > > Signed-off-by: Adham Abozaeid > --- >

Re: [PATCH] media: staging: tegra-vde: print long unsigned using %lu format specifier

2018-11-08 Thread Greg Kroah-Hartman
On Thu, Nov 08, 2018 at 11:02:24AM +, Colin King wrote: > From: Colin Ian King > > The frame.flags & FLAG_B_FRAME is promoted to a long unsigned because > of the use of the BIT() macro when defining FLAG_B_FRAME and causing a > build warning. Fix this by using the %lu format specifer. > >

[PATCH] media: staging: tegra-vde: print long unsigned using %lu format specifier

2018-11-08 Thread Colin King
From: Colin Ian King The frame.flags & FLAG_B_FRAME is promoted to a long unsigned because of the use of the BIT() macro when defining FLAG_B_FRAME and causing a build warning. Fix this by using the %lu format specifer. Cleans up warning: drivers/staging/media/tegra-vde/tegra-vde.c:267:5:

Re: [PATCH 3/3] staging: iio: ad7780: generates pattern_mask from PAT bits

2018-11-08 Thread Ardelean, Alexandru
On Wed, 2018-11-07 at 16:50 -0200, Giuliano Belinassi wrote: > Previously, all pattern_masks in the chip_info table were hardcoded. Now > they > are generated using the PAT macros, as described in the datasheets. > I like this change :) I only have nitpicks. See inline. > Signed-off-by:

Re: [PATCH 2/3] staging: iio: ad7780: check if ad778x before gain update

2018-11-08 Thread Ardelean, Alexandru
On Wed, 2018-11-07 at 16:50 -0200, Giuliano Belinassi wrote: > Only the ad778x have the 'gain' status bit. Check it before updating. > This looks good. The only note is that it can be squashed with the 1st patch (which I noted on the 1st patch). > Signed-off-by: Giuliano Belinassi > --- >

RE: [PATCH V2] binder: ipc namespace support for android binder

2018-11-08 Thread 周威
> From: Davidlohr Bueso > Sent: Thursday, November 8, 2018 3:00 PM > > On Mon, 29 Oct 2018, chouryzhou(??) wrote: > >@@ -63,6 +63,12 @@ struct ipc_namespace { > >unsigned intmq_msg_default; > >unsigned intmq_msgsize_default; > > > >+ /* next fields are for