[PATCH] x86/Hyper-V: Fix definition HV_MAX_FLUSH_REP_COUNT

From: Lan Tianyu The max flush rep count of HvFlushGuestPhysicalAddressList hypercall is equal with how many entries of union hv_gpa_page_range can be populated into the input parameter page. The origin code lacks parenthesis around PAGE_SIZE - 2 * sizeof(u64). This patch is to fix it. Cc: Fixs

[PATCH] staging: android: ashmem: Avoid range_alloc() allocation with ashmem_mutex held.

ashmem_pin() is calling range_shrink() without checking whether range_alloc() succeeded. Also, doing memory allocation with ashmem_mutex held should be avoided because ashmem_shrink_scan() tries to hold it. Therefore, move memory allocation for range_alloc() to ashmem_pin_unpin() and make range_al

Re: [PATCH v2 1/2] staging: iio: frequency: ad9834: Move frequency to standard iio types

Thank you for taking some time reviewing my code. Ad9833/ad9834 has two frequency and phase registers and only one output. The user can select which register is selected as input with a mux.Because I wanted to reduce as much as possible the custom attributes, I mapped the frequency 0 from register

Re: [PATCH] x86/Hyper-V: Fix definition HV_MAX_FLUSH_REP_COUNT

On Fri, Feb 22, 2019 at 06:48:44PM +0800, lantianyu1...@gmail.com wrote: > From: Lan Tianyu > > The max flush rep count of HvFlushGuestPhysicalAddressList hypercall > is equal with how many entries of union hv_gpa_page_range can be populated > into the input parameter page. The origin code lacks

[PATCH V3 1/10] X86/Hyper-V: Add parameter offset for hyperv_fill_flush_guest_mapping_list()

From: Lan Tianyu Add parameter offset to specify start position to add flush ranges in guest address list of struct hv_guest_mapping_flush_list. Signed-off-by: Lan Tianyu --- arch/x86/hyperv/nested.c| 4 ++-- arch/x86/include/asm/mshyperv.h | 2 +- arch/x86/kvm/vmx/vmx.c | 2 +

[PATCH V3 00/10] X86/KVM/Hyper-V: Add HV ept tlb range list flush support in KVM

From: Lan Tianyu This patchset is to introduce hv ept tlb range list flush function support in the KVM MMU component. Flushing ept tlbs of several address range can be done via single hypercall and new list flush function is used in the kvm_mmu_commit_zap_page() and FNAME(sync_page). This patchse

RE: [PATCH V3 1/10] X86/Hyper-V: Add parameter offset for hyperv_fill_flush_guest_mapping_list()

int hyperv_fill_flush_guest_mapping_list( struct hv_guest_mapping_flush_list *flush, - u64 start_gfn, u64 pages) + int offset, u64 start_gfn, u64 pages) { u64 cur = start_gfn; u64 additional_pages; - int gpa_n = 0; + int gpa_n

Re: [PATCH V3 00/10] X86/KVM/Hyper-V: Add HV ept tlb range list flush support in KVM

On 22/02/19 16:06, lantianyu1...@gmail.com wrote: > From: Lan Tianyu > > This patchset is to introduce hv ept tlb range list flush function > support in the KVM MMU component. Flushing ept tlbs of several address > range can be done via single hypercall and new list flush function is > used in th

Re: [PATCH v4] staging: nrf24: add new driver for 2.4GHz radio transceiver

On Tue, Feb 19, 2019 at 11:20:10AM +0100, Greg Kroah-Hartman wrote: > On Wed, Feb 13, 2019 at 08:40:35PM +0100, Marcin Ciupak wrote: > > This patch adds driver for Nordic Semiconductor nRF24L01+ radio > > transceiver. > > > > Signed-off-by: Marcin Ciupak > > --- > > Changes in v2: > > - add ter

[PATCH net] staging: fsl-dpaa2: ethsw: Add missing netdevice check

port_switchdev_event() does not check that the target network device is actually backed by the ethsw driver, this could be problematic in a stacked environment case. Fixes: 44baaa43d7cc ("staging: fsl-dpaa2/ethsw: Add Freescale DPAA2 Ethernet Switch driver") Signed-off-by: Florian Fainelli ---

[PATCH net-next 0/8] net: Remove switchdev_ops

Hi all, This patch series completes the removal of the switchdev_ops by converting switchdev_port_attr_set() to use either the blocking (process) or non-blocking (atomic) notifier since we typically need to deal with both depending on where in the bridge code we get called from. This was tested w

[PATCH net-next 3/8] net: dsa: Handle SWITCHDEV_PORT_ATTR_SET

Following patches will change the way we communicate setting a port's attribute and use notifiers towards that goal. Prepare DSA to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_SET from both atomic and process context and use a small helper to translate the event notifier into s

[PATCH net-next 8/8] net: Remove switchdev_ops

Now that we have converted all possible callers to using a switchdev notifier for attributes we do not have a need for implementing switchdev_ops anymore, and this can be removed from all drivers the net_device structure. Signed-off-by: Florian Fainelli --- .../net/ethernet/mellanox/mlxsw/spectr

[PATCH net-next 6/8] staging: fsl-dpaa2: ethsw: Handle SWITCHDEV_PORT_ATTR_SET

Following patches will change the way we communicate setting a port's attribute and use a blocking notifier to perform those tasks. Prepare ethsw to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_SET and simply translate that into the existing swdev_port_attr_set() call. Signed-o

[PATCH net-next 5/8] net: mscc: ocelot: Handle SWITCHDEV_PORT_ATTR_SET

Following patches will change the way we communicate setting a port's attribute and use notifiers to perform those tasks. Ocelot does not currently have an atomic notifier registered for switchdev events, so we need to register one in order to deal with atomic context SWITCHDEV_PORT_ATTR_SET event

[PATCH net-next 1/8] switchdev: Add SWITCHDEV_PORT_ATTR_SET

In preparation for allowing switchdev enabled drivers to veto specific attribute settings from within the context of the caller, introduce a new switchdev notifier type for port attributes. Suggested-by: Ido Schimmel Signed-off-by: Florian Fainelli --- include/net/switchdev.h | 27 +++

[PATCH net-next 7/8] net: switchdev: Replace port attr set SDO with a notification

Drop switchdev_ops.switchdev_port_attr_set. Drop the uses of this field from all clients, which were migrated to use switchdev notification in the previous patches. Add a new function switchdev_port_attr_notify() that sends the switchdev notifications SWITCHDEV_PORT_ATTR_SET and takes care, depend

[PATCH net-next 4/8] mlxsw: spectrum_switchdev: Handle SWITCHDEV_PORT_ATTR_SET

Following patches will change the way we communicate setting a port's attribute and use a notifier to perform those tasks. Prepare mlxsw to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_SET and utilize the switchdev_handle_port_attr_set() to handle stacking of devices. Signed-of

[PATCH net-next 2/8] rocker: Handle SWITCHDEV_PORT_ATTR_SET

Following patches will change the way we communicate setting a port's attribute and use notifiers towards that goal. Prepare rocker to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_SET from both atomic and process context and use a small helper to translate the event notifier int

[PATCH 1/8] switchdev: Add SWITCHDEV_PORT_ATTR_SET

In preparation for allowing switchdev enabled drivers to veto specific attribute settings from within the context of the caller, introduce a new switchdev notifier type for port attributes. Suggested-by: Ido Schimmel Signed-off-by: Florian Fainelli --- include/net/switchdev.h | 27 +++

[PATCH] staging/ks7070: Removed unused varibale

but not used [-Wunused-but-set-variable] u16 mib_val_size; drivers/staging/ks7010/ks_hostif.c:786:6: warning: variable ‘result_code’ set but not used [-Wunused-but-set-variable] u16 result_code; Remove these variables. Rebase on next-20190222 Cc: Greg Kroah-Hartman Cc: Sergio

Re: [PATCH] staging/ks7070: Removed unused varibale

variable] > u16 result_code; > > Remove these variables. > > Rebase on next-20190222 > > Cc: Greg Kroah-Hartman > Cc: Sergio Paracuellos > Cc: Quytelda Kahja > > Signed-off-by: Bo Yu > --- > drivers/staging/ks7010/ks_hostif.c | 6 -- > 1 file c

Re: [PATCH] staging/ks7070: Removed unused varibale

-but-set-variable] > u16 result_code; > > Remove these variables. > > Rebase on next-20190222 ^^^ Is this a v2 patch or something? Don't include this in the changelog. Put it under the --- cut off line. > > Cc: Greg Kroah-Hartman >

[PATCH V2] staging: ks7070: removed unused varibales

but not used [-Wunused-but-set-variable] u16 mib_val_size; drivers/staging/ks7010/ks_hostif.c:786:6: warning: variable ‘result_code’ set but not used [-Wunused-but-set-variable] u16 result_code; Remove these variables. Rebase on next-20190222 V2: fix patch format Cc: Greg Kroah

Re: [PATCH V2] staging: ks7070: removed unused varibales

next-20190222 V2: fix patch format Please drop it, will send V3 Thanks Cc: Greg Kroah-Hartman Cc: Sergio Paracuellos Cc: Quytelda Kahja Signed-off-by: Bo Yu --- drivers/staging/ks7010/ks_hostif.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/staging/ks7010/ks_hostif.c b

Re: [PATCH V2] staging: ks7070: removed unused varibales

variable] > u16 result_code; > > Remove these variables. > > Rebase on next-20190222 > V2: fix patch format As Dan has just said, this two rebase and v2 stuff is not needed in the changelog. Please, put it under the --- cut off line. > > Cc: Greg Kroah-Hartman >

Re: [PATCH] staging/ks7070: Removed unused varibale

-but-set-variable] > u16 result_code; > > Remove these variables. > > Rebase on next-20190222 > > Cc: Greg Kroah-Hartman > Cc: Sergio Paracuellos > Cc: Quytelda Kahja > > Signed-off-by: Bo Yu > --- > drivers/staging/ks7010/ks_hostif.c | 6 -- > 1 fi

[PATCH V3] staging: ks7010: removed unused variables

From: Bo Yu Compiling the kernel with W=1 results in the following warning: drivers/staging/ks7010/ks_hostif.c:465:6: warning: variable ‘mib_val_type’ set but not used [-Wunused-but-set-variable] u16 mib_val_type; drivers/staging/ks7010/ks_hostif.c:464:6: warning: variable ‘mib_val_size’ set