{"push_id":2430705184,"size":49,"distinct_size":1,"ref":"refs/heads/lineage-15.1","head":"c254c58b4f6afe0beae7b2a2cff5d3a6dd8eb7ed","before":"2c762f1bcbe174543f1ecc3748d4bc15dc98cb85","commits":[{"sha":"911e850bc967ff7c00524f4d8f068ce8a7a12695","author":{"name":"Santeri Toivonen","email":"16335dbd5705823f38136c77224dd839ad9c6262@vatsul.com"},"message":"platform/x86: asus-nb-wmi: Add wapf4 quirk for the X302UA\n\n\n[ Upstream commit f35823619db8bbaa2afea8705f239c3cecb9d22f ]\n\nAsus laptop X302UA starts up with Wi-Fi disabled,\nwithout a way to enable it. Set wapf=4 to fix the problem.\n\nSigned-off-by: Santeri Toivonen <santeri.toivonen@vatsul.com>\nSigned-off-by: Darren Hart (VMware) <dvhart@infradead.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/911e850bc967ff7c00524f4d8f068ce8a7a12695"},{"sha":"50655ac3bc2f9ec73d828896c70f6be2229d4f29","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"x86: i8259: export legacy_pic symbol\n\n\n[ Upstream commit 7ee06cb2f840a96be46233181ed4557901a74385 ]\n\nThe classic PC rtc-coms driver has a workaround for broken ACPI device\nnodes for it which lack an irq resource. This workaround used to\nunconditionally hardcode the irq to 8 in these cases.\n\nThis was causing irq conflict problems on systems without a legacy-pic\nso a recent patch added an if (nr_legacy_irqs()) guard to the\nworkaround to avoid this irq conflict.\n\nnr_legacy_irqs() uses the legacy_pic symbol under the hood causing\nan undefined symbol error if the rtc-cmos code is build as a module.\n\nThis commit exports the legacy_pic symbol to fix this.\n\nCc: rtc-linux@googlegroups.com\nCc: alexandre.belloni@free-electrons.com\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/50655ac3bc2f9ec73d828896c70f6be2229d4f29"},{"sha":"177bea46fe929297547441508a48589fe4331daa","author":{"name":"Dmitry Torokhov","email":"e82e0cc9230e3683c557741cb5a2c8321ee072ee@gmail.com"},"message":"Input: ar1021_i2c - fix too long name in driver's device table\n\n\n[ Upstream commit 95123fc43560d6f4a60e74f72836e63cd8848f76 ]\n\nThe name field in structure i2c_device_id is 20 characters, and we expect\nit to be NULL-terminated, however we are trying to stuff it with 21 bytes\nand thus NULL-terminator is lost. This causes issues when one creates\ndevice with name \"MICROCHIP_AR1021_I2C\" as i2c core cuts off the last \"C\",\nand automatic module loading by alias does not work as result.\n\nThe -I2C suffix in the device name is superfluous, we know what bus we are\ndealing with, so let's drop it. Also, no other driver uses capitals, and\nthe manufacturer name is normally not included, except in very rare cases\nof incompatible name collisions.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=116211\nFixes: dd4cae8bf166 (\"Input: Add Microchip AR1021 i2c touchscreen\")\nReviewed-By: Christian Gmeiner <christian.gmeiner@gmail.com>\nTested-by: Martin Kepplinger <martin.kepplinger@ginzinger.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/177bea46fe929297547441508a48589fe4331daa"},{"sha":"2d2cfeb58d8c120a95150006bc39063db2b7ac54","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"ACPI/processor: Replace racy task affinity logic\n\n\n[ Upstream commit 8153f9ac43897f9f4786b30badc134fcc1a4fb11 ]\n\nacpi_processor_get_throttling() requires to invoke the getter function on\nthe target CPU. This is achieved by temporarily setting the affinity of the\ncalling user space thread to the requested CPU and reset it to the original\naffinity afterwards.\n\nThat's racy vs. CPU hotplug and concurrent affinity settings for that\nthread resulting in code executing on the wrong CPU and overwriting the\nnew affinity setting.\n\nacpi_processor_get_throttling() is invoked in two ways:\n\n1) The CPU online callback, which is already running on the target CPU and\n   obviously protected against hotplug and not affected by affinity\n   settings.\n\n2) The ACPI driver probe function, which is not protected against hotplug\n   during modprobe.\n\nSwitch it over to work_on_cpu() and protect the probe function against CPU\nhotplug.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Fenghua Yu <fenghua.yu@intel.com>\nCc: Tony Luck <tony.luck@intel.com>\nCc: Herbert Xu <herbert@gondor.apana.org.au>\nCc: \"Rafael J. Wysocki\" <rjw@rjwysocki.net>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Sebastian Siewior <bigeasy@linutronix.de>\nCc: Lai Jiangshan <jiangshanlai@gmail.com>\nCc: linux-acpi@vger.kernel.org\nCc: Viresh Kumar <viresh.kumar@linaro.org>\nCc: Michael Ellerman <mpe@ellerman.id.au>\nCc: Tejun Heo <tj@kernel.org>\nCc: \"David S. Miller\" <davem@davemloft.net>\nCc: Len Brown <lenb@kernel.org>\nLink: http://lkml.kernel.org/r/20170412201042.785920903@linutronix.de\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/2d2cfeb58d8c120a95150006bc39063db2b7ac54"},{"sha":"fad89533e0d5067d38ffd119b4eee5e19d945821","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"cpufreq/sh: Replace racy task affinity logic\n\n\n[ Upstream commit 205dcc1ecbc566cbc20acf246e68de3b080b3ecf ]\n\nThe target() callback must run on the affected cpu. This is achieved by\ntemporarily setting the affinity of the calling thread to the requested CPU\nand reset it to the original affinity afterwards.\n\nThat's racy vs. concurrent affinity settings for that thread resulting in\ncode executing on the wrong CPU.\n\nReplace it by work_on_cpu(). All call pathes which invoke the callbacks are\nalready protected against CPU hotplug.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nCc: Fenghua Yu <fenghua.yu@intel.com>\nCc: Tony Luck <tony.luck@intel.com>\nCc: Herbert Xu <herbert@gondor.apana.org.au>\nCc: \"Rafael J. Wysocki\" <rjw@rjwysocki.net>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Sebastian Siewior <bigeasy@linutronix.de>\nCc: linux-pm@vger.kernel.org\nCc: Lai Jiangshan <jiangshanlai@gmail.com>\nCc: Michael Ellerman <mpe@ellerman.id.au>\nCc: Tejun Heo <tj@kernel.org>\nCc: \"David S. Miller\" <davem@davemloft.net>\nCc: Len Brown <lenb@kernel.org>\nLink: http://lkml.kernel.org/r/20170412201042.958216363@linutronix.de\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/fad89533e0d5067d38ffd119b4eee5e19d945821"},{"sha":"093c265afffb0a91a7611c3bb74d0883731a807b","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"genirq: Use irqd_get_trigger_type to compare the trigger type for shared IRQs\n\n\n[ Upstream commit 382bd4de61827dbaaf5fb4fb7b1f4be4a86505e7 ]\n\nWhen requesting a shared irq with IRQF_TRIGGER_NONE then the irqaction\nflags get filled with the trigger type from the irq_data:\n\n        if (!(new->flags & IRQF_TRIGGER_MASK))\n                new->flags |= irqd_get_trigger_type(&desc->irq_data);\n\nOn the first setup_irq() the trigger type in irq_data is NONE when the\nabove code executes, then the irq is started up for the first time and\nthen the actual trigger type gets established, but that's too late to fix\nup new->flags.\n\nWhen then a second user of the irq requests the irq with IRQF_TRIGGER_NONE\nits irqaction's triggertype gets set to the actual trigger type and the\nfollowing check fails:\n\n        if (!((old->flags ^ new->flags) & IRQF_TRIGGER_MASK))\n\nResulting in the request_irq failing with -EBUSY even though both\nusers requested the irq with IRQF_SHARED | IRQF_TRIGGER_NONE\n\nFix this by comparing the new irqaction's trigger type to the trigger type\nstored in the irq_data which correctly reflects the actual trigger type\nbeing used for the irq.\n\nSuggested-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nAcked-by: Marc Zyngier <marc.zyngier@arm.com>\nLink: http://lkml.kernel.org/r/20170415100831.17073-1-hdegoede@redhat.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/093c265afffb0a91a7611c3bb74d0883731a807b"},{"sha":"e69880c86c7391e7a78eb05faa736fa77a7cf8a7","author":{"name":"Edgar Cherkasov","email":"fafbd70fec4c79dfd6464c5691681cf6725fdd02@dev.rtsoft.ru"},"message":"i2c: i2c-scmi: add a MS HID\n\n\n[ Upstream commit e058e7a4bc89104540a8a303682248614b5df6f1 ]\n\nDescription of the problem:\n - i2c-scmi driver contains only two identifiers \"SMBUS01\" and \"SMBUSIBM\";\n - the fist HID (SMBUS01) is clearly defined in \"SMBus Control Method\n   Interface Specification, version 1.0\": \"Each device must specify\n   'SMBUS01' as its _HID and use a unique _UID value\";\n - unfortunately, BIOS vendors (like AMI) seem to ignore this requirement\n   and implement \"SMB0001\" HID instead of \"SMBUS01\";\n - I speculate that they do this because only \"SMB0001\" is hard coded in\n   Windows SMBus driver produced by Microsoft.\n\nThis leads to following situation:\n - SMBus works out of box in Windows but not in Linux;\n - board vendors are forced to add correct \"SMBUS01\" HID to BIOS to make\n   SMBus work in Linux. Moreover the same board vendors complain that\n   tools (3-rd party ASL compiler) do not like the \"SMBUS01\" identifier\n   and produce errors.  So they need to constantly patch the compiler for\n   each new version of BIOS.\n\nAs it is very unlikely that BIOS vendors implement a correct HID in\nfuture, I would propose to consider whether it is possible to work around\nthe problem by adding MS HID to the Linux i2c-scmi driver.\n\nv2: move the definition of the new HID to the driver itself.\n\nSigned-off-by: Edgar Cherkasov <echerkasov@dev.rtsoft.ru>\nSigned-off-by: Michael Brunner <Michael.Brunner@kontron.com>\nAcked-by: Viktor Krasnov <vkrasnov@dev.rtsoft.ru>\nReviewed-by: Jean Delvare <jdelvare@suse.de>\nReviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/e69880c86c7391e7a78eb05faa736fa77a7cf8a7"},{"sha":"f566bb949757cb3312e31b79400c30103d4a8434","author":{"name":"David Ahern","email":"e530dc8f30cd5fef67eca6e0378269caad10dfeb@cumulusnetworks.com"},"message":"net: ipv6: send unsolicited NA on admin up\n\n\n[ Upstream commit 4a6e3c5def13c91adf2acc613837001f09af3baa ]\n\nndisc_notify is the ipv6 equivalent to arp_notify. When arp_notify is\nset to 1, gratuitous arp requests are sent when the device is brought up.\nThe same is expected when ndisc_notify is set to 1 (per ndisc_notify in\nDocumentation/networking/ip-sysctl.txt). The NA is not sent on NETDEV_UP\nevent; add it.\n\nFixes: 5cb04436eef6 (\"ipv6: add knob to send unsolicited ND on link-layer address change\")\nSigned-off-by: David Ahern <dsa@cumulusnetworks.com>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/f566bb949757cb3312e31b79400c30103d4a8434"},{"sha":"eba5af302e5c42711feaa5bd07cf36ee64e15a22","author":{"name":"Jasmin J","email":"6046dd04c6c537c644f417d4b83456467b79920a@anw.at"},"message":"media/dvb-core: Race condition when writing to CAM\n\n\n[ Upstream commit e7080d4471d805d921a9ea21b32f911a91e248cb ]\n\nIt started with a sporadic message in syslog: \"CAM tried to send a\nbuffer larger than the ecount size\" This message is not the fault\nitself, but a consecutive fault, after a read error from the CAM. This\nhappens only on several CAMs, several hardware, and of course sporadic.\n\nIt is a consecutive fault, if the last read from the CAM did fail. I\nguess this will not happen on all CAMs, but at least it did on mine.\nThere was a write error to the CAM and during the re-initialization\nprocedure, the CAM finished the last read, although it got a RS.\n\nThe write error to the CAM happened because a race condition between HC\nwrite, checking DA and FR.\n\nThis patch added an additional check for DA(RE), just after checking FR.\nIt is important to read the CAMs status register again, to give the CAM\nthe necessary time for a proper reaction to HC. Please note the\ndescription within the source code (patch below).\n\n[mchehab@s-opensource.com: make checkpatch happy]\n\nSigned-off-by: Jasmin jessich <jasmin@anw.at>\nTested-by: Ralph Metzler <rjkm@metzlerbros.de>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/eba5af302e5c42711feaa5bd07cf36ee64e15a22"},{"sha":"65e796250cfb067092357bddf44cea97e9e1c717","author":{"name":"Marek Vasut","email":"467844f9788017470d85adaf2186777024d3d5ee@denx.de"},"message":"spi: dw: Disable clock after unregistering the host\n\n\n[ Upstream commit 400c18e3dc86e04ef5afec9b86a8586ca629b9e9 ]\n\nThe dw_mmio driver disables the block clock before unregistering\nthe host. The code unregistering the host may access the SPI block\nregisters. If register access happens with block clock disabled,\nthis may lead to a bus hang. Disable the clock after unregistering\nthe host to prevent such situation.\n\nThis bug was observed on Altera Cyclone V SoC.\n\nSigned-off-by: Marek Vasut <marex@denx.de>\nCc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nCc: Mark Brown <broonie@kernel.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/65e796250cfb067092357bddf44cea97e9e1c717"},{"sha":"be5f85e3f355d4afe72e387e7b7fae054f731b51","author":{"name":"Mohammed Shafi Shajakhan","email":"4abf9d4e9fb909a6b0c1689ab80ea0e519567492@qti.qualcomm.com"},"message":"ath: Fix updating radar flags for coutry code India\n\n\n[ Upstream commit c0c345d4cacc6a1f39d4856f37dcf6e34f51a5e4 ]\n\nAs per latest regulatory update for India, channel 52, 56, 60, 64\nis no longer restricted to DFS. Enabling DFS/no infra flags in driver\nresults in applying all DFS related restrictions (like doing CAC etc\nbefore this channel moves to 'available state') for these channels\neven though the country code is programmed as 'India' in he hardware,\nfix this by relaxing the frequency range while applying RADAR flags\nonly if the country code is programmed to India. If the frequency range\nneeds to modified based on different country code, ath_is_radar_freq\ncan be extended/modified dynamically.\n\nSigned-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/be5f85e3f355d4afe72e387e7b7fae054f731b51"},{"sha":"dec444b63dee03febc0abe04db6fe680b2c99c2b","author":{"name":"David Gibson","email":"d8099b0f90e53c29d29eb12a7a3caa5af4f12681@gibson.dropbear.id.au"},"message":"scsi: virtio_scsi: Always try to read VPD pages\n\n\n[ Upstream commit 25d1d50e23275e141e3a3fe06c25a99f4c4bf4e0 ]\n\nPassed through SCSI targets may have transfer limits which come from the\nhost SCSI controller or something on the host side other than the target\nitself.\n\nTo make this work properly, the hypervisor can adjust the target's VPD\ninformation to advertise these limits.  But for that to work, the guest\nhas to look at the VPD pages, which we won't do by default if it is an\nSPC-2 device, even if it does actually support it.\n\nThis adds a workaround to address this, forcing devices attached to a\nvirtio-scsi controller to always check the VPD pages.  This is modelled\non a similar workaround for the storvsc (Hyper-V) SCSI controller,\nalthough that exists for slightly different reasons.\n\nA specific case which causes this is a volume from IBM's IPR RAID\ncontroller (which presents as an SPC-2 device, although it does support\nVPD) passed through with qemu's 'scsi-block' device.\n\n[mkp: fixed typo]\n\nSigned-off-by: David Gibson <david@gibson.dropbear.id.au>\nAcked-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/dec444b63dee03febc0abe04db6fe680b2c99c2b"},{"sha":"0a4063b03ba4a76765705adb997124cbe7900938","author":{"name":"Alexey Kardashevskiy","email":"4ac31ea3affe1efd3f0ea903dab9f9666559912c@ozlabs.ru"},"message":"KVM: PPC: Book3S PR: Exit KVM on failed mapping\n\n\n[ Upstream commit bd9166ffe624000140fc6b606b256df01fc0d060 ]\n\nAt the moment kvmppc_mmu_map_page() returns -1 if\nmmu_hash_ops.hpte_insert() fails for any reason so the page fault handler\nresumes the guest and it faults on the same address again.\n\nThis adds distinction to kvmppc_mmu_map_page() to return -EIO if\nmmu_hash_ops.hpte_insert() failed for a reason other than full pteg.\nAt the moment only pSeries_lpar_hpte_insert() returns -2 if\nplpar_pte_enter() failed with a code other than H_PTEG_FULL.\nOther mmu_hash_ops.hpte_insert() instances can only fail with\n-1 \"full pteg\".\n\nWith this change, if PR KVM fails to update HPT, it can signal\nthe userspace about this instead of returning to guest and having\nthe very same page fault over and over again.\n\nSigned-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>\nReviewed-by: David Gibson <david@gibson.dropbear.id.au>\nSigned-off-by: Paul Mackerras <paulus@ozlabs.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/0a4063b03ba4a76765705adb997124cbe7900938"},{"sha":"3a5294f03a10031a9407d01287e6ccc800304bf3","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"tcp: remove poll() flakes with FastOpen\n\n\n[ Upstream commit 0f9fa831aecfc297b7b45d4f046759bcefcf87f0 ]\n\nWhen using TCP FastOpen for an active session, we send one wakeup event\nfrom tcp_finish_connect(), right before the data eventually contained in\nthe received SYNACK is queued to sk->sk_receive_queue.\n\nThis means that depending on machine load or luck, poll() users\nmight receive POLLOUT events instead of POLLIN|POLLOUT\n\nTo fix this, we need to move the call to sk->sk_state_change()\nafter the (optional) call to tcp_rcv_fastopen_synack()\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nAcked-by: Yuchung Cheng <ycheng@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/3a5294f03a10031a9407d01287e6ccc800304bf3"},{"sha":"ae7579e5308cece1a10028b5aba0b8fa9ed06401","author":{"name":"Bernd Faust","email":"3ec39b0d09ec9d22df07e91d93bf18a0b109a021@gmail.com"},"message":"e1000e: fix timing for 82579 Gigabit Ethernet controller\n\n\n[ Upstream commit 5313eeccd2d7f486be4e5c7560e3e2be239ec8f7 ]\n\nAfter an upgrade to Linux kernel v4.x the hardware timestamps of the\n82579 Gigabit Ethernet Controller are different than expected.\nThe values that are being read are almost four times as big as before\nthe kernel upgrade.\n\nThe difference is that after the upgrade the driver sets the clock\nfrequency to 25MHz, where before the upgrade it was set to 96MHz. Intel\nconfirmed that the correct frequency for this network adapter is 96MHz.\n\nSigned-off-by: Bernd Faust <berndfaust@gmail.com>\nAcked-by: Sasha Neftin <sasha.neftin@intel.com>\nAcked-by: Jacob Keller <jacob.e.keller@intel.com>\nTested-by: Aaron Brown <aaron.f.brown@intel.com>\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/ae7579e5308cece1a10028b5aba0b8fa9ed06401"},{"sha":"2ead2134a1859bd75c8b34d9bf020b289341eaac","author":{"name":"Mikhail Paulyshka","email":"b4a5ea001e047040e8c9075b67a268293138da2c@mixaill.tk"},"message":"ALSA: hda - Fix headset microphone detection for ASUS N551 and N751\n\n\n[ Upstream commit fc7438b1eb12b6c93d7b7a62423779eb5dfc673c ]\n\nHeadset microphone does not work out of the box on ASUS Nx51\nlaptops. This patch fixes it.\n\nPatch tested on Asus N551 laptop. Asus N751 part is not tested, but\naccording to [1] this laptop uses the same audiosystem.\n\n1. https://bugzilla.kernel.org/show_bug.cgi?id=117781\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195437\nSigned-off-by: Mikhail Paulyshka <me@mixaill.tk>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/2ead2134a1859bd75c8b34d9bf020b289341eaac"},{"sha":"bff38ff05503e2161d6fe2d6e1979db4e9b80e46","author":{"name":"Feras Daoud","email":"005832ac8f0780bc0fab40c8ce2d77cdbb2c5097@mellanox.com"},"message":"IB/ipoib: Update broadcast object if PKey value was changed in index 0\n\n\n[ Upstream commit 9a9b8112699d78e7f317019b37f377e90023f3ed ]\n\nUpdate the broadcast address in the priv->broadcast object when the\nPkey value changes in index 0, otherwise the multicast GID value will\nkeep the previous value of the PKey, and will not be updated.\nThis leads to interface state down because the interface will keep the\nold PKey value.\n\nFor example, in SR-IOV environment, if the PF changes the value of PKey\nindex 0 for one of the VFs, then the VF receives PKey change event that\ntriggers heavy flush. This flush calls update_parent_pkey that update the\nbroadcast object and its relevant members. If in this case the multicast\nGID will not be updated, the interface state will be down.\n\nFixes: c2904141696e (\"IPoIB: Fix pkey change flow for virtualization environments\")\nSigned-off-by: Feras Daoud <ferasda@mellanox.com>\nSigned-off-by: Erez Shitrit <erezsh@mellanox.com>\nReviewed-by: Alex Vesker <valex@mellanox.com>\nSigned-off-by: Leon Romanovsky <leon@kernel.org>\nSigned-off-by: Doug Ledford <dledford@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/bff38ff05503e2161d6fe2d6e1979db4e9b80e46"},{"sha":"21bdd575943daef3c951ecd3dd70ef62bb9f065e","author":{"name":"Dan Carpenter","email":"60b2bf2bc0bec4ca4a4b046ca7ef9255248abff8@oracle.com"},"message":"HSI: ssi_protocol: double free in ssip_pn_xmit()\n\n\n[ Upstream commit 3026050179a3a9a6f5c892c414b5e36ecf092081 ]\n\nIf skb_pad() fails then it frees skb and we don't need to free it again\nat the end of the function.\n\nFixes: dc7bf5d7 (\"HSI: Introduce driver for SSI Protocol\")\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Sebastian Reichel <sre@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/21bdd575943daef3c951ecd3dd70ef62bb9f065e"},{"sha":"c84d2e72f5dd07d6a3fc4195a2b8574ba8f7721d","author":{"name":"James Smart","email":"852f67cd5ef747ea235926255e543a67292b5596@gmail.com"},"message":"Fix driver usage of 128B WQEs when WQ_CREATE is V1.\n\n\n[ Upstream commit 3f247de750b8dd8f50a2c1390e2a1238790a9dff ]\n\nThere are two versions of a structure for queue creation and setup that the\ndriver shares with FW. The driver was only treating as version 0.\n\nVerify WQ_CREATE with 128B WQEs in V0 and V1.\n\nCode review of another bug showed the driver passing\n128B WQEs and 8 pages in WQ CREATE and V0.\nCode inspection/instrumentation showed that the driver\nuses V0 in WQ_CREATE and if the caller passes queue->entry_size\n128B, the driver sets the hdr_version to V1 so all is good.\nWhen I tested the V1 WQ_CREATE, the mailbox failed causing\nthe driver to unload.\n\nSigned-off-by: Dick Kennedy <dick.kennedy@broadcom.com>\nSigned-off-by: James Smart <james.smart@broadcom.com>\nReviewed-by: Johannes Thumshirn <jthumshirn@suse.de>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/c84d2e72f5dd07d6a3fc4195a2b8574ba8f7721d"},{"sha":"fc0808f0c2a43212f73d438e083a34251984540c","author":{"name":"Dan Carpenter","email":"60b2bf2bc0bec4ca4a4b046ca7ef9255248abff8@oracle.com"},"message":"mmc: host: omap_hsmmc: checking for NULL instead of IS_ERR()\n\n\n[ Upstream commit ec5ab8933772c87f24ad62a4a602fe8949f423c2 ]\n\ndevm_pinctrl_get() returns error pointers, it never returns NULL.\n\nFixes: 455e5cd6f736 (\"mmc: omap_hsmmc: Pin remux workaround to support SDIO interrupt on AM335x\")\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nReviewed-by: Kishon Vijay Abraham I <kishon@ti.com>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op3/commits/fc0808f0c2a43212f73d438e083a34251984540c"}]}
{"actor":{"display_login":"nathanchance"}}