linux-next: remove the pcmcia tree

Hi all, The pcmcia tree (git://git.kernel.org/pub/scm/linux/kernel/git/brodo/linux.git#pcmcia-next) has not been updated in more than a year, so I have removed it from linux-next. Please let me know if/when you want it reinstated. -- Cheers, Stephen Rothwell pgpbACrVOT79P.pgp Description: Ope

linux-next: cleanup the kgdb trees

Hi all, The kgdb tree (git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git#kgdb-next) has not been updated in more than a year, so I have rmeoved it from linux-next. It contained: 3bd67b37e350 kdb: print real address of pointers instead of hashed addresses a0ca72c2d1ac kdb: use correc

[PATCH v7 0/3] Logitech HID++ Bluetooth LE support

This series allows hid-logitech-hidpp to support Bluetooth LE HID++ devices. Only the MX Master is added right now but more HID++ Bluetooth LE devices can be added once they are tested. Thanks, Mazin Changes since [v6]: - Based patch on "HID: logitech-hidpp: rework device validation"

[PATCH v7 1/3] HID: logitech-hidpp: Support translations from short to long reports

This patch allows short reports to be translated into long reports. hidpp_validate_device now returns a u8 instead of a bool which represents the supported reports. The corresponding bits (i.e. HIDPP_REPORT_*_SUPPORTED) are set if an HID++ report is supported. If a short report is being sent and

[PATCH v7 2/3] HID: logitech-hidpp: Support MX Master (b012, b01e) over Bluetooth

This patch adds support for the MX Master over Bluetooth (b012, b01e). I have only added the devices that have been tested, so the 0xb017 variant of the MX Master needs to be added once it is tested. Since this patch series adds support for Bluetooth LE devices in general, other Bluetooth LE devi

[PATCH v7 3/3] HID: logitech-hidpp: Support WirelessDeviceStatus connect events

This patch allows hidpp_report_is_connect_event to support WirelessDeviceStatus connect events. The WirelessDeviceStatus feature index is stored in hidpp_device when probed. The connect event's fap feature_index is compared against it if the device supports it. Thanks, Mazin Signed-off-by: Mazin

Re: sparse: __pure declaration only

On Fri, Oct 18, 2019 at 08:31:48AM -0700, Linus Torvalds wrote: > On Fri, Oct 18, 2019 at 4:15 AM Ben Dooks wrote: > > > > is this a valid warning? if not, should sparse be ignoring these. > > It's technically valid, but maybe it's not useful. > > If we make sure that any pure bits from a declar

Re: [PATCH v2] rtlwifi: Fix potential overflow on P2P code

Laura Abbott writes: > On 10/19/19 6:51 AM, Kalle Valo wrote: >> Laura Abbott writes: >> >>> Nicolas Waisman noticed that even though noa_len is checked for >>> a compatible length it's still possible to overrun the buffers >>> of p2pinfo since there's no check on the upper bound of noa_num. >>>

Re: [PATCH] tty: serial: msm_serial: Fix flow control

On Sat 19 Oct 14:06 PDT 2019, Jeffrey Hugo wrote: > hci_qca interfaces to the wcn3990 via a uart_dm on the msm8998 mtp and > Lenovo Miix 630 laptop. As part of initializing the wcn3990, hci_qca > disables flow, configures the uart baudrate, and then reenables flow - at > which point an event is e

<    1   2   3