[PATCH 4.18 164/228] IB/hfi1: Fix context recovery when PBC has an UnsupportedVL

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit d623500b3c4efd8d4e945ac9003c6b87b469a9ab upstream. If a packet stream uses an UnsupportedVL (virtual lane), the send engine will not send the packet, and it will not ind

[PATCH 4.18 182/228] bpf, sockmap: fix sock_hash_alloc and reject zero-sized keys

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit b845c898b2f1ea458d5453f0fa1da6e2dfce3bb4 ] Currently, it is possible to create a sock hash map with key size of 0 and have the kernel return a fd back to user

[PATCH 4.18 176/228] thermal: of-thermal: disable passive polling when thermal zone is disabled

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anson Huang [ Upstream commit 152395fd03d4ce1e535a75cdbf58105e50587611 ] When thermal zone is in passive mode, disabling its mode from sysfs is NOT taking effect at all, it is still polling th

[PATCH 4.14 029/137] ARM: hwmod: RTC: Dont assume lock/unlock will be called with irq enabled

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Gerlach [ Upstream commit 6d609b35c815ba20132b7b64bcca04516bb17c56 ] When the RTC lock and unlock functions were introduced it was likely assumed that they would always be called from irq

[PATCH 4.14 030/137] x86/entry/64: Add two more instruction suffixes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich [ Upstream commit 6709812f094d96543b443645c68daaa32d3d3e77 ] Sadly, other than claimed in: a368d7fd2a ("x86/entry/64: Add instruction suffix") ... there are two more instances

[PATCH 4.18 212/228] hwmon: (adt7475) Make adt7475_read_word() return errors

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit f196dec6d50abb2e65fb54a0621b2f1b4d922995 ] The adt7475_read_word() function was meant to return negative error codes on failure. Signed-off-by: Dan Carpenter

[PATCH 4.14 011/137] power: vexpress: fix corruption in notifier registration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla [ Upstream commit 09bebb1adb21ecd04adf7ccb3b06f73e3a851e93 ] Vexpress platforms provide two different restart handlers: SYS_REBOOT that restart the entire system, while DB_RESET o

[PATCH 4.14 004/137] vmci: type promotion bug in qp_host_get_user_memory()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 7fb2fd4e25fc1fb10dcb30b5519de257cfeae84c ] The problem is that if get_user_pages_fast() fails and returns a negative error code, it gets type promoted to a high

[PATCH 4.18 203/228] ice: Fix potential return of uninitialized value

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Brandeburg [ Upstream commit dab0588fb616c1774bbf108eab1749dda4ac6942 ] In ice_vsi_setup_[tx|rx]_rings, err is uninitialized which can result in a garbage value return to the caller. Fix

[PATCH 4.14 027/137] media: staging/imx: fill vb2_v4l2_buffer field entry

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Seiderer [ Upstream commit a38d4b71cb7a12b65317f4e3d59883a918957719 ] - fixes gstreamer v4l2src warning: 0:00:00.716640334 349 0x164f720 WARN v4l2bufferpool gstv4l2bufferpool.c:11

[PATCH 4.14 007/137] power: supply: axp288_charger: Fix initial constant_charge_current value

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede [ Upstream commit f2a42595f0865886a2d40524b0e9d15600848670 ] We should look at val which contains the value read from the register, not ret which is always 0 on a successful read

[PATCH 4.18 128/228] ARM: dts: dra7: fix DCAN node addresses

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Hilman [ Upstream commit 949bdcc8a97c6078f21c8d4966436b117f2e4cd3 ] Fix the DT node addresses to match the reg property addresses, which were verified to match the TRM: http://www.ti.com

[PATCH 4.18 173/228] qed: Wait for MCP halt and resume commands to take place

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit 76271809f49056f079e202bf6513d17b0d6dd34d ] Successive iterations of halting and resuming the management chip (MCP) might fail, since currently the driver doesn't

[PATCH 4.18 120/228] staging: pi433: fix race condition in pi433_ioctl

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Hugo Lefeuvre [ Upstream commit 6de4ef65a8c6f53ce7eef0410bc3b6e4b624 ] In the PI433_IOC_WR_TX_CFG case in pi433_ioctl, instance->tx_cfg is modified via copy_from_user(&instance->tx_cfg, a

Re: [linux-sunxi] Re: [PATCH 08/12] drm/sun4i: sun6i_mipi_dsi: Refactor vertical video start delay

On Mon, Oct 01, 2018 at 01:25:59PM +0530, Jagan Teki wrote: > On Saturday 29 September 2018 08:57 PM, Maxime Ripard wrote: > > On Thu, Sep 27, 2018 at 11:03:19PM +0530, Jagan Teki wrote: > > > On Thu, Sep 27, 2018 at 10:44 PM Maxime Ripard > > > wrote: > > > > > > > > On Thu, Sep 27, 2018 at 05:1

[PATCH 4.18 156/228] USB: remove LPM management from usb_driver_claim_interface()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit c183813fcee44a249339b7c46e1ad271ca1870aa upstream. usb_driver_claim_interface() disables and re-enables Link Power Management, but it shouldn't do either one, for the reasons

[PATCH 4.18 144/228] spi: rspi: Fix invalid SPI use during system suspend

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit c1ca59c22c56930b377a665fdd1b43351887830b upstream. If the SPI queue is running during system suspend, the system may lock up. Fix this by stopping/restarting the que

[PATCH 4.18 159/228] filesystem-dax: Fix use of zero page

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Matthew Wilcox commit b90ca5cc32f59bb214847c6855959702f00c6801 upstream. Use my_zero_pfn instead of ZERO_PAGE(), and pass the vaddr to it instead of zero so it works on MIPS and s390 who refer

[PATCH 4.18 145/228] spi: rspi: Fix interrupted DMA transfers

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 8dbbaa47b96f6ea5f09f922b4e3c505cd8cf upstream. When interrupted, wait_event_interruptible_timeout() returns -ERESTARTSYS, and the SPI transfer in progress will fa

[PATCH 4.18 155/228] Revert "usb: cdc-wdm: Fix a sleep-in-atomic-context bug in service_outstanding_interrupt()"

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit e871db8d78df1c411032cbb3acfdf8930509360e upstream. This reverts commit 6e22e3af7bb3a7b9dc53cb4687659f6e63fca427. The bug the patch describes to, has been alre

[PATCH 4.18 154/228] USB: usbdevfs: restore warning for nonsensical flags

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 81e0403b26d94360abd1f6a57311337973bc82cd upstream. If we filter flags before they reach the core we need to generate our own warnings. Signed-off-by: Oliver Neukum Fixes

[PATCH 4.18 157/228] uaccess: Fix is_source param for check_copy_size() in copy_to_iter_mcsafe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dave Jiang commit dfb06cba8c73c0704710b2e3fbe2c35ac66a01b4 upstream. copy_to_iter_mcsafe() is passing in the is_source parameter as "false" to check_copy_size(). This is different than what co

[PATCH 4.18 160/228] Input: elantech - enable middle button of touchpad on ThinkPad P72

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Ma commit 91a97507323e1ad4bfc10f4a5922e67cdaf8b3cd upstream. Adding 2 new touchpad IDs to support middle button support. Cc: sta...@vger.kernel.org Signed-off-by: Aaron Ma Signed-off-b

[PATCH 4.18 150/228] usb: roles: Take care of driver module reference counting

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 5c54fcac9a9de559b444ac63ec3cd82f1d157a0b upstream. This fixes potential "BUG: unable to handle kernel paging request at ..." from happening. Cc: Acked-by: Hans de Goed

[PATCH 4.18 151/228] usb: core: safely deal with the dynamic quirk lists

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Harry Pan commit 16c4cb19fa85c648a803752eb63cac0ef69231c2 upstream. Applying dynamic usbcore quirks in early booting when the slab is not yet ready would cause kernel panic of null pointer der

[PATCH 4.18 161/228] IB/srp: Avoid that sg_reset -d ${srp_device} triggers an infinite loop

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit ee92efe41cf358f4b99e73509f2bfd4733609f26 upstream. Use different loop variables for the inner and outer loop. This avoids that an infinite loop occurs if there are more

[PATCH 4.18 146/228] regulator: fix crash caused by null driver data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yu Zhao commit fb6de923ca3358a91525552b4907d4cb38730bdd upstream. dev_set_drvdata() needs to be called before device_register() exposes device to userspace. Otherwise kernel crashes after it g

[PATCH 4.18 141/228] spi: tegra20-slink: explicitly enable/disable clock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Marcel Ziswiler commit 7001cab1dabc0b72b2b672ef58a90ab64f5e2343 upstream. Depending on the SPI instance one may get an interrupt storm upon requesting resp. interrupt unless the clock is expli

[PATCH 4.18 122/228] ath10k: snoc: use correct bus-specific pointer in RX retry

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris [ Upstream commit 426a0f0b5a2fe1df3496ba299ee3521159dba302 ] We're 'ath10k_snoc', not 'ath10k_pci'. This probably means we're accessing junk data in ath10k_snoc_rx_replenish_retry

[PATCH 4.18 140/228] intel_th: Fix resource handling for ACPI glue layer

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit ebe4582281d6e90972f057318a6edea14810ea48 upstream. The core of the driver expects the resource array from the glue layer to be indexed by even numbers, as is the case

Re: [PATCH v4 2/5] drm/dp: fix link probing for devices supporting DP 1.4+

On Mon, Oct 01, 2018 at 11:27:08AM +0200, Quentin Schulz wrote: > Hi Manasi, > > On Fri, Sep 21, 2018 at 12:59:30AM -0700, Manasi Navare wrote: > > Thanks for the patch. Verified with the DP 1.4 spec and looks good to me. > > Also look at the related patch that makes use of the correct extended >

[PATCH 4.18 081/228] ALSA: hda: Add AZX_DCAPS_PM_RUNTIME for AMD Raven Ridge

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng [ Upstream commit 1adca4b0cd65c14cb8b8c9c257720385869c3d5f ] This patch can make audio controller in AMD Raven Ridge gets runtime suspended to D3, to save ~1W power when it's not

[PATCH 4.18 134/228] x86/mm: Expand static page table for fixmap space

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Feng Tang commit 05ab1d8a4b36ee912b7087c6da127439ed0a903e upstream. We met a kernel panic when enabling earlycon, which is due to the fixmap address of earlycon is not statically setup. Curre

[PATCH 4.18 138/228] serial: cpm_uart: return immediately from console poll

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit be28c1e3ca29887e207f0cbcd294cefe5074bab6 upstream. kgdb expects poll function to return immediately and returning NO_POLL_CHAR when no character is available. Fixes: f

[PATCH 4.18 133/228] block: fix deadline elevator drain for zoned block devices

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Damien Le Moal commit 854f31ccdd7964c9c2e68da234a3a8aedb51cf6b upstream. When the deadline scheduler is used with a zoned block device, writes to a zone will be dispatched one at a time. This

[PATCH 4.18 137/228] serial: mvebu-uart: Fix reporting of effective CSIZE to userspace

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kiszka commit e0bf2d4982fe7d9ddaf550dd023803ea286f47fc upstream. Apparently, this driver (or the hardware) does not support character length settings. It's apparently running in 8-bit mode

[PATCH 4.18 108/228] spi: orion: fix CS GPIO handling again

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kundrát [ Upstream commit fb9acf5f1f21f1de193523ff780bda375b4c2e21 ] The code did not de-assert any CS GPIOs before probing slaves. This means that several CS signals could be active at on

[PATCH 4.18 107/228] scsi: hisi_sas: Fix the conflict between dev gone and host reset

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Xiaofei Tan [ Upstream commit d2fc401e47529d9ffd2673a5395d56002e31ad98 ] There is a possible conflict when a device is removed and host reset occurs concurrently. The reason is that then the

[PATCH 4.18 085/228] net: phy: xgmiitorgmii: Check phy_driver ready before accessing

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Brandon Maier [ Upstream commit ab4e6ee578e88a659938db8fbf33720bc048d29c ] Since a phy_device is added to the global mdio_bus list during phy_device_register(), but a phy_device's phy_driver d

[PATCH 4.18 102/228] arm64: dts: renesas: Fix VSPD registers range

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Pinchart [ Upstream commit e21adc781bb45e810f1c396c4bc2c1624a4c25b9 ] The VSPD and FCPVD nodes have overlapping register ranges, as the FCPVD devices are mapped in the memory range usu

[PATCH 4.18 121/228] ath10k: fix incorrect size of dma_free_coherent in ath10k_ce_alloc_src_ring_64

4.18-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit 5a211627004e2cddd0ab8b9df19e5fb0bbe97634 ] sizeof(struct ce_desc) should be a copy-paste mistake just use sizeof(struct ce_desc_64) to avoid mem leak Fixes: b7ba8

Re: [PATCH] ARM: makefile: use ARMv3M mode for RiscPC

On 2 October 2018 at 15:20, Jason A. Donenfeld wrote: > The purpose of CONFIG_CPU_32v3 is to avoid ldrh/strh on the RiscPC, > which is pretty much an ARMv4 device, except its bus will choke on the > half-words. The way to make the C compiler not output ldrh/strh is with > -march=armv3, which doesn

[PATCH 4.18 110/228] ASoC: Intel: bytcr_rt5640: Fix Acer Iconia 8 over-current detect threshold

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede [ Upstream commit f12a0a3c4cc6f594d7c2ea361f2396ae5c518d2c ] Change the over-current detect threshold on the Acer Iconia 8 from 2000ua to 1500uA, this fixes headset button presse

[PATCH 4.18 079/228] media: tm6000: add error handling for dvb_register_adapter

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyang Jia [ Upstream commit e95d7c6eb94c634852eaa5ff4caf3db05b5d2e86 ] When dvb_register_adapter fails, the lack of error-handling code may cause unexpected results. This patch adds error-

[PATCH 4.18 114/228] ASoC: dapm: Fix potential DAI widget pointer deref when linking DAIs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Liam Girdwood [ Upstream commit e01b4f624278d5efe5fb5da585ca371947b16680 ] Sometime a component or topology may configure a DAI widget with no private data leading to a dev_dbg() dereferencne

[PATCH 4.18 119/228] EDAC, altera: Fix an error handling path in altr_s10_sdram_probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 9d72fe1ce81bc757ecb6d57b58e5fd95b9ad1b26 ] If regmap_write() fails, we should release some resources as done in all the other error handling paths of the f

[PATCH 4.18 084/228] drm/sun4i: Enable DW HDMI PHY clock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jernej Skrabec [ Upstream commit 09773c532d30187f86a142901c27c93e629ce6ba ] Current DW HDMI PHY code never prepares and enables PHY clock after it is created. It's just used as it is. This may

[PATCH 4.18 101/228] MIPS: boot: fix build rule of vmlinux.its.S

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Masahiro Yamada [ Upstream commit 67e09db507db3e1642ddce512a4313d20addd6e5 ] As Documentation/kbuild/makefile.txt says, it is a typical mistake to forget the FORCE prerequisite for the rule in

[PATCH 4.18 096/228] Documentation/process: fix reST table border error

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit cccd289f12d0e827070c847b1ff96ba02eb20eaf ] Fix reST error in Documentation/process/: Documentation/process/2.Process.rst:131: ERROR: Malformed table. Bottom/hea

[PATCH 4.18 093/228] drm/omap: gem: Fix mm_list locking

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter [ Upstream commit 5117bd898e8c0a31e8ab3a9b8523aecf0706e997 ] - None of the list walkings where protected. - Switch to a mutex since the list walking at device resume time can

[PATCH 4.18 053/228] powerpc/powernv/ioda2: Reduce upper limit for DMA window size

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit d3d4ffaae439981e1e441ebb125aa3588627c5d8 ] We use PHB in mode1 which uses bit 59 to select a correct DMA window. However there is mode2 which uses bits 5

[PATCH 4.18 074/228] staging: mt7621-eth: Fix memory leak in mtk_add_mac() error path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kamal Heib [ Upstream commit 85e1d42663a0c163002961d2685be952067b0dc2 ] Fix memory leak in error path of mtk_add_mac() by make sure to free the allocated netdev. Fixes: e3cbf478f846 ('staging

[PATCH 4.18 092/228] wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 4ec7cece87b3ed21ffcd407c62fb2f151a366bc1 ] Otherwise we can get: WARNING: CPU: 0 PID: 55 at drivers/net/wireless/ti/wlcore/io.h:84 I've only seen this few tim

[PATCH 4.18 058/228] s390/dasd: correct numa_node in dasd_alloc_queue

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Gorbik [ Upstream commit b17e3abb0af404cb62ad4ef1a5962f58b06e2b78 ] The numa_node field of the tag_set struct has to be explicitly initialized, otherwise it stays as 0, which is a valid

[PATCH 4.18 089/228] rndis_wlan: potential buffer overflow in rndis_wlan_auth_indication()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit ae636fb1554833ee5133ca47bf4b2791b6739c52 ] This is a static checker fix, not something I have tested. The issue is that on the second iteration through the loo

[PATCH 4.18 069/228] media: soc_camera: ov772x: correct setting of banding filter

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 22216ec41e919682c15345e95928f266e8ba6f9e ] The banding filter ON/OFF is controlled via bit 5 of COM8 register. It is attempted to be enabled in ov772x_set_param

[PATCH 4.18 045/228] scsi: target/iscsi: Make iscsit_ta_authentication() respect the output buffer size

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 35bea5c84fd13c643cce63f0b5cd4b148f8c901d ] Fixes: e48354ce078c ("iscsi-target: Add iSCSI fabric support for target v4.1") Signed-off-by: Bart Van Assche Revi

[PATCH 4.18 078/228] staging: mt7621-dts: Fix remaining pcie warnings

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Rosen Penev [ Upstream commit d0233204fbc10f003d1ef077f57341c2feca4002 ] This currently fixes the remaining dtb warnings: Node /pcie@1e14/pcie0 has a reg or ranges property, but no unit n

[PATCH 4.18 042/228] ARM: hwmod: RTC: Dont assume lock/unlock will be called with irq enabled

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dave Gerlach [ Upstream commit 6d609b35c815ba20132b7b64bcca04516bb17c56 ] When the RTC lock and unlock functions were introduced it was likely assumed that they would always be called from irq

[PATCH 4.18 056/228] s390/sysinfo: add missing #ifdef CONFIG_PROC_FS

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens [ Upstream commit 9f35b818a2f90fb6cb291aa0c9f835d4f0974a9a ] Get rid of this compile warning for !PROC_FS: CC arch/s390/kernel/sysinfo.o arch/s390/kernel/sysinfo.c:275:1

[PATCH 4.18 067/228] ath10k: use locked skb_dequeue for rx completions

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bob Copeland [ Upstream commit 62652555c616cad23a572f76cb5e870ab5395191 ] In our environment we are occasionally seeing the following stack trace in ath10k: Unable to handle kernel paging req

[PATCH 4.18 075/228] drivers/tty: add error handling for pcmcia_loop_config

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyang Jia [ Upstream commit 85c634e919bd6ef17427f26a52920aeba12e16ee ] When pcmcia_loop_config fails, the lack of error-handling code may cause unexpected results. This patch adds error-ha

[PATCH 4.18 066/228] selftests: forwarding: Tweak tc filters for mirror-to-gretap tests

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Petr Machata [ Upstream commit ec9fdc99f5a6a2cfe4061e807fcb0cc1129f0a2d ] When running mirror_gre_bridge_1d_vlan tests on veth, several issues cause spurious failures: - vlan_ethtype should b

[PATCH 4.18 040/228] include/rdma/opa_addr.h: Fix an endianness issue

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 4eefd62c17a9a5e7576207e84f3d2b4f73aba750 ] IB_MULTICAST_LID_BASE is defined as follows: #define IB_MULTICAST_LID_BASE cpu_to_be16(0xC000) Hence use be16

[PATCH 4.18 039/228] IB/mlx5: Fix GRE flow specification

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Maor Gottlieb [ Upstream commit a93b632c4531ff50c43d658447a45cbc11f488fd ] Currently the driver sets the mask of the gre_protocol to 0x without consideration in the user request. Fix it b

[PATCH 4.18 062/228] iio: accel: adxl345: convert address field usage in iio_chan_spec

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 9048f1f18a70a01eaa3c8e7166fdb2538929d780 ] Currently the address field in iio_chan_spec is filled with an accel data register address for the corresponding axis.

[PATCH 4.18 007/228] net: hns3: Fix for mailbox message truncated problem

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Fuyun Liang [ Upstream commit ead5bd4d35c0a14d5ce1474177718c678dff5205 ] The payload of mailbox message is 16 byte and the value of HCLGE_MBX_MAX_ARQ_MSG_SIZE is 8. A message truncated problem

[PATCH 4.18 009/228] net: hns3: Fix warning bug when doing lp selftest

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yunsheng Lin [ Upstream commit d7099d15478e89edb9bc6c6e3ab4cd341884a367 ] The napi_alloc_skb is excepted to be called under the non-preemptible code path when it is called by hns3_clean_rx_rin

[PATCH 4.18 006/228] siox: dont create a thread without starting it

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Uwe Kleine-König [ Upstream commit e890591413819eeb604207ad3261ba617b2ec0bb ] When a siox master device is registered a kthread is created that is only started when triggered by userspace. So

[PATCH 4.18 024/228] power: remove possible deadlock when unregistering power_supply

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires [ Upstream commit 3ffa6583e24e1ad1abab836d24bfc9d2308074e5 ] If a device gets removed right after having registered a power_supply node, we might enter in a deadlock between

[PATCH 4.18 036/228] media: fsl-viu: fix error handling in viu_of_probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov [ Upstream commit 662a99e145661c2b35155cf375044deae9b79896 ] viu_of_probe() ignores fails in i2c_get_adapter(), tries to unlock uninitialized mutex on error path. The patch

[PATCH 4.18 019/228] Bluetooth: Add a new Realtek 8723DE ID 0bda:b009

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jian-Hong Pan [ Upstream commit 45ae68b8cfc25bdbffc11248001c47ab1b76ff6e ] Without this patch we cannot turn on the Bluethooth adapter on HP 14-bs007la. T: Bus=01 Lev=02 Prnt=03 Port=00 Cnt=

[PATCH 4.18 022/228] iommu/msm: Dont call iommu_device_{,un}link from atomic context

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel [ Upstream commit 379521462e4add27f3514da8e4ab1fd7a54fe1c7 ] Fixes the following splat during boot: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:

[PATCH 4.18 029/228] RDMA/bnxt_re: Fix a couple off by one bugs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 474e5a86067e5f12c97d1db8b170c7f45b53097a ] The sgid_tbl->tbl[] array is allocated in bnxt_qplib_alloc_sgid_tbl(). It has sgid_tbl->max elements. So the > shoul

[PATCH 4.18 017/228] power: vexpress: fix corruption in notifier registration

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla [ Upstream commit 09bebb1adb21ecd04adf7ccb3b06f73e3a851e93 ] Vexpress platforms provide two different restart handlers: SYS_REBOOT that restart the entire system, while DB_RESET o

[PATCH 4.18 018/228] iommu/amd: make sure TLB to be flushed before IOVA freed

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhen Lei [ Upstream commit 3c120143f584360a13614787e23ae2cdcb5e5ccd ] Although the mapping has already been removed in the page table, it maybe still exist in TLB. Suppose the freed IOVAs is r

[PATCH 4.18 016/228] uwb: hwa-rc: fix memory leak at probe

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit 11b71782c1d10d9bccc31825cf84291cd7588a1e ] hwarc_probe() allocates memory for hwarc, but does not free it if uwb_rc_add() or hwarc_get_version() fail. Found b

[PATCH 4.18 015/228] serial: sh-sci: Stop RX FIFO timer during port shutdown

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit c5a9262fa8bfed0dddc7466ef10fcd292e2af61b ] The RX FIFO timer may be armed when the port is shut down, hence the timer function may still be called afterwar

[PATCH 4.18 010/228] net: hns3: Fix get_vector ops in hclgevf_main module

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yunsheng Lin [ Upstream commit 03718db97bfb57535f3aa8110f0cbe0c616a67c0 ] The hclgevf_free_vector function expects the caller to pass the vector_id to it, and hclgevf_put_vector pass vector to

[PATCH 4.18 012/228] staging: rts5208: fix missing error check on call to rtsx_write_register

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit c5fae4f4fd28189b1062fb8ef7b21fec37cb8b17 ] Currently the check on error return from the call to rtsx_write_register is checking the error status from the previ

[PATCH 4.18 014/228] misc: sram: enable clock before registering regions

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit d5b9653dd2bb7a2b1c8cc783c5d3b607bbb6b271 ] Make sure to enable the clock before registering regions and exporting partitions to user space at which point we must

[PATCH 4.18 001/228] crypto: skcipher - Fix -Wstringop-truncation warnings

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Stafford Horne [ Upstream commit cefd769fd0192c84d638f66da202459ed8ad63ba ] As of GCC 9.0.0 the build is reporting warnings like: crypto/ablkcipher.c: In function ‘crypto_ablkcipher_repor

[PATCH 4.18 013/228] power: supply: axp288_charger: Fix initial constant_charge_current value

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede [ Upstream commit f2a42595f0865886a2d40524b0e9d15600848670 ] We should look at val which contains the value read from the register, not ret which is always 0 on a successful read

Re: [GIT PULL] MMC fixes for v4.19-rc7

On Tue, Oct 02, 2018 at 09:22:33AM +0200, Ulf Hansson wrote: > Hi Greg, > > Here's a PR with a few MMC fixes intended for v4.19-rc7. Details about the > highlights are found in the signed tag. > > Please pull this in! Now merged, thanks. greg k-h

[PATCH] ARM: makefile: use ARMv3M mode for RiscPC

The purpose of CONFIG_CPU_32v3 is to avoid ldrh/strh on the RiscPC, which is pretty much an ARMv4 device, except its bus will choke on the half-words. The way to make the C compiler not output ldrh/strh is with -march=armv3, which doesn't support them in the ISA. However, this prevents certain cryp

Re: [RFC][PATCH 3/3] locking/qspinlock: Optimize for x86

On Tue, Oct 02, 2018 at 02:31:52PM +0200, Andrea Parri wrote: > > consider this scenario with your patch: > > > > 1. CPU0 sees a locked val, and is about to do your xchg_relaxed() to set > >pending. > > > > 2. CPU1 comes in and sets pending, spins on locked > > > > 3. CPU2 sees a pending and

[PATCH 4/4] ARM: dts: at91: sama5d4_xplained: even nand memory partitions

sama5d4_xplained, ssam9x5cm, sama5d2_ptc_ek and sama5d3_xplained nand flashes have a common memory map. Even the nand memory partitions to match our NAND flash map available at: http://www.at91.com/linux4sam/pub/Linux4SAM/SambaSubsections//demo_nandflash_map_lnx4sam5x.png Signed-off-by: Tudor Amb

[PATCH 3/4] ARM: dts: at91: sama5d3_xplained: even nand memory partitions

sama5d3_xplained, sam9x5cm, sama5d2_ptc_ek and sama5d4_xplained nand flashes have a common memory map. Even the nand memory partitions to match our nand flash map available at: http://www.at91.com/linux4sam/pub/Linux4SAM/SambaSubsections//demo_nandflash_map_lnx4sam5x.png Signed-off-by: Tudor Amba

[PATCH 2/4] ARM: dts: at91: at91sam9x5cm: even nand memory partitions

sam9x5cm, sama5d2_ptc_ek, sama5d3_xplained and sama5d4_xplained nand flashes have a common memory map. Even the nand memory partitions to match our nand flash map available at: http://www.at91.com/linux4sam/pub/Linux4SAM/SambaSubsections//demo_nandflash_map_lnx4sam5x.png Signed-off-by: Tudor Amba

[PATCH 1/4] ARM: dts: at91: sama5d2_ptc_ek: fix bootloader env offsets

The offsets for the bootloader environment and its redundant partition were inverted. Fix the addresses to match our nand flash map available at: http://www.at91.com/linux4sam/pub/Linux4SAM/SambaSubsections//demo_nandflash_map_lnx4sam5x.png Signed-off-by: Tudor Ambarus --- arch/arm/boot/dts/at9

[PATCH 0/4] ARM: dts: at91: even nand memory partitions

sam9x5cm, sama5d2_ptc_ek, sama5d3_xplained and sama5d4_xplained nand flashes have a common memory map. Even the nand memory partitions to match our NAND flash map available at: http://www.at91.com/linux4sam/pub/Linux4SAM/SambaSubsections//demo_nandflash_map_lnx4sam5x.png Tudor Ambarus (4): ARM:

Re: [RFC][PATCH 2/3] locking/qspinlock: Rework some comments

Hi Peter, On Mon, Oct 01, 2018 at 09:10:22PM +0200, Peter Zijlstra wrote: > On Mon, Oct 01, 2018 at 06:17:08PM +0100, Will Deacon wrote: > > On Wed, Sep 26, 2018 at 01:01:19PM +0200, Peter Zijlstra wrote: > > > + > > > /* > > > - * If we observe any contention; undo and queue. > > > + * If we

Re: [RFC][PATCH 3/3] locking/qspinlock: Optimize for x86

On Mon, Oct 01, 2018 at 10:00:28PM +0200, Peter Zijlstra wrote: > On Mon, Oct 01, 2018 at 06:17:00PM +0100, Will Deacon wrote: > > Thanks for chewing up my afternoon ;) > > I'll get you a beer in EDI ;-) Just one?! > > But actually, > > consider this scenario with your patch: > > > > 1. CPU0 se

Re: [PATCH v7 06/14] sched/topology: Reference the Energy Model of CPUs when available

On Tuesday 02 Oct 2018 at 14:36:17 (+0200), Peter Zijlstra wrote: > On Wed, Sep 12, 2018 at 10:13:01AM +0100, Quentin Perret wrote: > > +struct perf_domain { > > + struct em_perf_domain *obj; > > + struct perf_domain *next; > > + struct rcu_head rcu; > > +}; > > Maybe s/obj/em_pd/ or somethi

Re: [PATCH] bus: fsl-mc: explicitly define the fsl_mc_command endianness

On 02.10.2018 15:16, Ioana Ciornei wrote: > Both the header and the command parameters of the fsl_mc_command are > 64-bit little-endian words. Use the appropriate type to explicitly > specify their endianness. > > Signed-off-by: Ioana Ciornei Reviewed-By: Laurentiu Tudor --- Best Regards, Lau

darowizna

Witam, Nie mam innego sposobu, żeby się z Tobą skontaktować, niż wysłać ci tego e-maila. Jestem w rozpaczy, a moje serce krwawi, gdy piszę to przesłanie, które, mam nadzieję, będzie przyciągało twoją uwagę. Kontaktuję się z tobą dzisiaj, ponieważ bardzo prawdziwe, że tego nie wiemy, nie powstr

Re: [PATCH 1/2] arm64: dts: allwinner: Olimex A64-OLinuXino: enable eMMC.

On Sat, Sep 29, 2018 at 01:51:02PM -0300, Rodrigo Exterckötter Tjäder wrote: > On Sat, Sep 29, 2018 at 12:47 PM Maxime Ripard > wrote: > > > > On Thu, Sep 27, 2018 at 11:49:20AM -0300, Rodrigo Exterckötter Tjäder wrote: > > > On Thu, Sep 27, 2018 at 5:17 AM Maxime Ripard > > > wrote: > > > > > >

Re: [PATCH] ARM: makefile: pass -march=armv4 to assembler even on CPU32v3

Hey Ard, On Tue, Oct 2, 2018 at 3:10 PM Ard Biesheuvel wrote: > > It builds but it doesn't run, at least not when built into the kernel > proper (which will be the case after random.c moves to this library) > > Your toolchain is implicitly passing --fix-v4bx to the assembler, > which causes it to

[PATCH v7 8/8] selftests, arm64: add a selftest for passing tagged pointers to kernel

This patch adds a simple test, that calls the uname syscall with a tagged user pointer as an argument. Without the kernel accepting tagged user pointers the test fails with EFAULT. Signed-off-by: Andrey Konovalov --- tools/testing/selftests/arm64/.gitignore | 1 + tools/testing/selftests/a

[PATCH v7 4/8] mm, arm64: untag user addresses in mm/gup.c

mm/gup.c provides a kernel interface that accepts user addresses and manipulates user pages directly (for example get_user_pages, that is used by the futex syscall). Since a user can provided tagged addresses, we need to handle such case. Add untagging to gup.c functions that use user addresses fo

<    4   5   6   7   8   9   10   11   12   >