{"push_id":1371289870,"size":119,"distinct_size":119,"ref":"refs/heads/master","head":"46390b4d67c99ae0b4b47fe491ee59c57ab8fbb4","before":"c1111611b60c13f2740b36b3e5874cdff3b018f0","commits":[{"sha":"5f1875cb9a5e3f8b3a4ff27c967e7c8950fd5b4a","author":{"name":"Adam Lee","email":"6f3b8e5f2eab2b8871ede59de67de41ed112b2e8@canonical.com"},"message":"Bluetooth: ath3k: workaround the compatibility issue with xHCI controller\n\ncommit c561a5753dd631920c4459a067d22679b3d110d6 upstream.\n\nBugLink: https://bugs.launchpad.net/bugs/1400215\n\nath3k devices fail to load firmwares on xHCI buses, but work well on\nEHCI, this might be a compatibility issue between xHCI and ath3k chips.\nAs my testing result, those chips will work on xHCI buses again with\nthis patch.\n\nThis workaround is from Qualcomm, they also did some workarounds in\nWindows driver.\n\nSigned-off-by: Adam Lee <adam.lee@canonical.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/5f1875cb9a5e3f8b3a4ff27c967e7c8950fd5b4a"},{"sha":"1ac28faf499e0d12b54c26f997a8ff1e9b59b5f2","author":{"name":"Dave Chinner","email":"6091b9ca93c3bf202a7dfb4ab952b5e043623b84@redhat.com"},"message":"xfs: ensure buffer types are set correctly\n\ncommit 0d612fb570b71ea2e49554a770cff4c489018b2c upstream.\n\nJan Kara reported that log recovery was finding buffers with invalid\ntypes in them. This should not happen, and indicates a bug in the\nlogging of buffers. To catch this, add asserts to the buffer\nformatting code to ensure that the buffer type is in range when the\ntransaction is committed.\n\nWe don't set a type on buffers being marked stale - they are not\ngoing to get replayed, the format item exists only for recovery to\nbe able to prevent replay of the buffer, so the type does not\nmatter. Hence that needs special casing here.\n\nReported-by: Jan Kara <jack@suse.cz>\nTested-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Brian Foster <bfoster@redhat.com>\nSigned-off-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/1ac28faf499e0d12b54c26f997a8ff1e9b59b5f2"},{"sha":"0bb774e475e17e25dee471ec7e118fbc2c196a5f","author":{"name":"Dave Chinner","email":"6091b9ca93c3bf202a7dfb4ab952b5e043623b84@redhat.com"},"message":"xfs: inode unlink does not set AGI buffer type\n\ncommit f19b872b086711bb4b22c3a0f52f16aa920bcc61 upstream.\n\nThis leads to log recovery throwing errors like:\n\nXFS (md0): Mounting V5 Filesystem\nXFS (md0): Starting recovery (logdev: internal)\nXFS (md0): Unknown buffer type 0!\nXFS (md0): _xfs_buf_ioapply: no ops on block 0xaea8802/0x1\nffff8800ffc53800: 58 41 47 49 .....\n\nWhich is the AGI buffer magic number.\n\nEnsure that we set the type appropriately in both unlink list\naddition and removal.\n\nTested-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Brian Foster <bfoster@redhat.com>\nSigned-off-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/0bb774e475e17e25dee471ec7e118fbc2c196a5f"},{"sha":"c745405133dec61af5f6ac513343b6021537cfe5","author":{"name":"Dave Chinner","email":"6091b9ca93c3bf202a7dfb4ab952b5e043623b84@redhat.com"},"message":"xfs: set superblock buffer type correctly\n\ncommit 3443a3bca54588f43286b725d8648d33a38c86f1 upstream.\n\nWhen the superblock is modified in a transaction, the commonly\nmodified fields are not actually copied to the superblock buffer to\navoid the buffer lock becoming a serialisation point. However, there\nare some other operations that modify the superblock fields within\nthe transaction that don't directly log to the superblock but rely\non the changes to be applied during the transaction commit (to\nminimise the buffer lock hold time).\n\nWhen we do this, we fail to mark the buffer log item as being a\nsuperblock buffer and that can lead to the buffer not being marked\nwith the corect type in the log and hence causing recovery issues.\nFix it by setting the type correctly, similar to xfs_mod_sb()...\n\nTested-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Brian Foster <bfoster@redhat.com>\nSigned-off-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/c745405133dec61af5f6ac513343b6021537cfe5"},{"sha":"5527b059b946cdc201618255602c0d180c3c1629","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"fsnotify: fix handling of renames in audit\n\ncommit 6ee8e25fc3e916193bce4ebb43d5439e1e2144ab upstream.\n\nCommit e9fd702a58c4 (\"audit: convert audit watches to use fsnotify\ninstead of inotify\") broke handling of renames in audit.  Audit code\nwants to update inode number of an inode corresponding to watched name\nin a directory.  When something gets renamed into a directory to a\nwatched name, inotify previously passed moved inode to audit code\nhowever new fsnotify code passes directory inode where the change\nhappened.  That confuses audit and it starts watching parent directory\ninstead of a file in a directory.\n\nThis can be observed for example by doing:\n\n  cd /tmp\n  touch foo bar\n  auditctl -w /tmp/foo\n  touch foo\n  mv bar foo\n  touch foo\n\nIn audit log we see events like:\n\n  type=CONFIG_CHANGE msg=audit(1423563584.155:90): auid=1000 ses=2 op=\"updated rules\" path=\"/tmp/foo\" key=(null) list=4 res=1\n  ...\n  type=PATH msg=audit(1423563584.155:91): item=2 name=\"bar\" inode=1046884 dev=08:0 2 mode=0100644 ouid=0 ogid=0 rdev=00:00 nametype=DELETE\n  type=PATH msg=audit(1423563584.155:91): item=3 name=\"foo\" inode=1046842 dev=08:0 2 mode=0100644 ouid=0 ogid=0 rdev=00:00 nametype=DELETE\n  type=PATH msg=audit(1423563584.155:91): item=4 name=\"foo\" inode=1046884 dev=08:0 2 mode=0100644 ouid=0 ogid=0 rdev=00:00 nametype=CREATE\n  ...\n\nand that's it - we see event for the first touch after creating the\naudit rule, we see events for rename but we don't see any event for the\nlast touch.  However we start seeing events for unrelated stuff\nhappening in /tmp.\n\nFix the problem by passing moved inode as data in the FS_MOVED_FROM and\nFS_MOVED_TO events instead of the directory where the change happens.\nThis doesn't introduce any new problems because noone besides\naudit_watch.c cares about the passed value:\n\n  fs/notify/fanotify/fanotify.c cares only about FSNOTIFY_EVENT_PATH events.\n  fs/notify/dnotify/dnotify.c doesn't care about passed 'data' value at all.\n  fs/notify/inotify/inotify_fsnotify.c uses 'data' only for FSNOTIFY_EVENT_PATH.\n  kernel/audit_tree.c doesn't care about passed 'data' at all.\n  kernel/audit_watch.c expects moved inode as 'data'.\n\nFixes: e9fd702a58c49db (\"audit: convert audit watches to use fsnotify instead of inotify\")\nSigned-off-by: Jan Kara <jack@suse.cz>\nCc: Paul Moore <paul@paul-moore.com>\nCc: Eric Paris <eparis@redhat.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/5527b059b946cdc201618255602c0d180c3c1629"},{"sha":"e1cb0f8f2bcbca8bed926e27f47e71860e64eb40","author":{"name":"Emmanuel Grumbach","email":"8b9b3ed0afbc1fa5fc02c3dc29b7819d4e9d8433@intel.com"},"message":"iwlwifi: pcie: disable the SCD_BASE_ADDR when we resume from WoWLAN\n\ncommit cd8f438405032ac8ff88bd8f2eca5e0c0063b14b upstream.\n\nThe base address of the scheduler in the device's memory\n(SRAM) comes from two different sources. The periphery\nregister and the alive notification from the firmware.\nWe have a check in iwl_pcie_tx_start that ensures that\nthey are the same.\nWhen we resume from WoWLAN, the firmware may have crashed\nfor whatever reason. In that case, the whole device may be\nreset which means that the periphery register will hold a\nmeaningless value. When we come to compare\ntrans_pcie->scd_base_addr (which really holds the value we\nhad when we loaded the WoWLAN firmware upon suspend) and\nthe current value of the register, we don't see a match\nunsurprisingly.\nTrick the check to avoid a loud yet harmless WARN.\nNote that when the WoWLAN has crashed, we will see that\nin iwl_trans_pcie_d3_resume which will let the op_mode\nknow. Once the op_mode is informed that the WowLAN firmware\nhas crashed, it can't do much besides resetting the whole\ndevice.\n\nReviewed-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/e1cb0f8f2bcbca8bed926e27f47e71860e64eb40"},{"sha":"a5cea574ffde2ddd7d863b249ffd8414cb6266c8","author":{"name":"Eyal Shapira","email":"4e9d7dd2c54b7b667a2a0ebb731d836a5b44a6be@wizery.com"},"message":"iwlwifi: mvm: validate tid and sta_id in ba_notif\n\ncommit 2cee4762c528a9bd2cdff793197bf591a2196c11 upstream.\n\nThese are coming from the FW and are used to access arrays.\nBad values can cause an out of bounds access so discard\nsuch ba_notifs and warn.\n\nSigned-off-by: Eyal Shapira <eyalx.shapira@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/a5cea574ffde2ddd7d863b249ffd8414cb6266c8"},{"sha":"7372b2873953bbc90b3cae6c0be914e7d59e95cb","author":{"name":"Luciano Coelho","email":"907a6d4087ac6e6523ff3c213269cab2819d38b5@intel.com"},"message":"iwlwifi: mvm: fix failure path when power_update fails in add_interface\n\ncommit fd66fc1cafd72ddf27dbec3a5e29e99839d1bc84 upstream.\n\nWhen iwl_mvm_power_update_mac() is called, we have already added the\nmac context, so if this call fails we should remove the mac.\n\nFixes: commit e5e7aa8e2561 ('iwlwifi: mvm: refactor power code')\nSigned-off-by: Luciano Coelho <luciano.coelho@intel.com>\nReviewed-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/7372b2873953bbc90b3cae6c0be914e7d59e95cb"},{"sha":"9232bf0ddbf31468da38d748d79aaddebd9ba70f","author":{"name":"Luciano Coelho","email":"907a6d4087ac6e6523ff3c213269cab2819d38b5@intel.com"},"message":"iwlwifi: mvm: always use mac color zero\n\ncommit 5523d11cc46393a1e61b7ef4a0b2d4e7ed9521e4 upstream.\n\nWe don't really need to use different mac colors when adding mac\ncontexts, because they're not used anywhere.  In fact, the firmware\ndoesn't accept 255 as a valid color, so we get into a SYSASSERT 0x3401\nwhen we reach that.\n\nRemove the color increment to use always zero and avoid reaching 255.\n\nSigned-off-by: Luciano Coelho <luciano.coelho@intel.com>\nReviewed-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/9232bf0ddbf31468da38d748d79aaddebd9ba70f"},{"sha":"87316349cbbb317ba659630e27965615f34b88f0","author":{"name":"Seth Forshee","email":"7eef0d67708f72385bb42d10e516f71c5f708675@canonical.com"},"message":"HID: i2c-hid: Limit reads to wMaxInputLength bytes for input events\n\ncommit 6d00f37e49d95e640a3937a4a1ae07dbe92a10cb upstream.\n\nd1c7e29e8d27 (HID: i2c-hid: prevent buffer overflow in early IRQ)\nchanged hid_get_input() to read ihid->bufsize bytes, which can be\nmore than wMaxInputLength. This is the case with the Dell XPS 13\n9343, and it is causing events to be missed. In some cases the\nmissed events are releases, which can cause the cursor to jump or\nfreeze, among other problems. Limit the number of bytes read to\nmin(wMaxInputLength, ihid->bufsize) to prevent such problems.\n\nFixes: d1c7e29e8d27 \"HID: i2c-hid: prevent buffer overflow in early IRQ\"\nSigned-off-by: Seth Forshee <seth.forshee@canonical.com>\nReviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/87316349cbbb317ba659630e27965615f34b88f0"},{"sha":"e0a5548dcadf134b1bf5a4243d803ab673919220","author":{"name":"Ricardo Ribalda Delgado","email":"1d916c4e2e300e3102d4ef191eab8464e77b0533@gmail.com"},"message":"PCI: Generate uppercase hex for modalias var in uevent\n\ncommit 145b3fe579db66fbe999a2bc3fd5b63dffe9636d upstream.\n\nSome implementations of modprobe fail to load the driver for a PCI device\nautomatically because the \"interface\" part of the modalias from the kernel\nis lowercase, and the modalias from file2alias is uppercase.\n\nThe \"interface\" is the low-order byte of the Class Code, defined in PCI\nr3.0, Appendix D.  Most interface types defined in the spec do not use\nalpha characters, so they won't be affected.  For example, 00h, 01h, 10h,\n20h, etc. are unaffected.\n\nPrint the \"interface\" byte of the Class Code in uppercase hex, as we\nalready do for the Vendor ID, Device ID, Class, etc.\n\nCommit 89ec3dcf17fd (\"PCI: Generate uppercase hex for modalias interface\nclass\") fixed only half of the problem.  Some udev implementations rely on\nthe uevent file and not the modalias file.\n\nFixes: d1ded203adf1 (\"PCI: add MODALIAS to hotplug event for pci devices\")\nFixes: 89ec3dcf17fd (\"PCI: Generate uppercase hex for modalias interface class\")\nSigned-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nAcked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/e0a5548dcadf134b1bf5a4243d803ab673919220"},{"sha":"a316a636bd2239ae4bf549c26ca12161c0daef7d","author":{"name":"Michel Dänzer","email":"04e02e363b23f600e6da8ae785c28c5ce9396c71@amd.com"},"message":"PCI: Fix infinite loop with ROM image of size 0\n\ncommit 16b036af31e1456cb69243a5a0c9ef801ecd1f17 upstream.\n\nIf the image size would ever read as 0, pci_get_rom_size() could keep\nprocessing the same image over and over again.  Exit the loop if we ever\nread a length of zero.\n\nThis fixes a soft lockup on boot when the radeon driver calls\npci_get_rom_size() on an AMD Radeon R7 250X PCIe discrete graphics card.\n\n[bhelgaas: changelog, reference]\nLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386973\nReported-by: Federico <federicotg@gmail.com>\nSigned-off-by: Michel Dänzer <michel.daenzer@amd.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nReviewed-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/a316a636bd2239ae4bf549c26ca12161c0daef7d"},{"sha":"8fb18a3df2df961b48c1c0774245ebed380e2ddb","author":{"name":"Mikulas Patocka","email":"a2da12c8268d5a95fc65964f0061e0e46206d68d@redhat.com"},"message":"cpufreq: speedstep-smi: enable interrupts when waiting\n\ncommit d4d4eda23794c701442e55129dd4f8f2fefd5e4d upstream.\n\nOn Dell Latitude C600 laptop with Pentium 3 850MHz processor, the\nspeedstep-smi driver sometimes loads and sometimes doesn't load with\n\"change to state X failed\" message.\n\nThe hardware sometimes refuses to change frequency and in this case, we\nneed to retry later. I found out that we need to enable interrupts while\nwaiting. When we enable interrupts, the hardware blockage that prevents\nfrequency transition resolves and the transition is possible. With\ndisabled interrupts, the blockage doesn't resolve (no matter how long do\nwe wait). The exact reasons for this hardware behavior are unknown.\n\nThis patch enables interrupts in the function speedstep_set_state that can\nbe called with disabled interrupts. However, this function is called with\ndisabled interrupts only from speedstep_get_freqs, so it shouldn't cause\nany problem.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/8fb18a3df2df961b48c1c0774245ebed380e2ddb"},{"sha":"b79de759626440e590feb8c12e0e7d7b9b320291","author":{"name":"Malcolm Priestley","email":"e187a437af0ab791fc51b0acfa7691f617a012f3@gmail.com"},"message":"lmedm04: Fix usb_submit_urb BOGUS urb xfer, pipe 1 != type 3 in interrupt urb\n\ncommit 15e1ce33182d1d5dbd8efe8d382b9352dc857527 upstream.\n\nA quirk of some older firmwares that report endpoint pipe type as PIPE_BULK\nbut the endpoint otheriwse functions as interrupt.\n\nCheck if usb_endpoint_type is USB_ENDPOINT_XFER_BULK and set as usb_rcvbulkpipe.\n\nSigned-off-by: Malcolm Priestley <tvboxspy@gmail.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/b79de759626440e590feb8c12e0e7d7b9b320291"},{"sha":"984cc9c1ae6e5c17bd3d6221c1cb5a9a239325d8","author":{"name":"Dan Carpenter","email":"60b2bf2bc0bec4ca4a4b046ca7ef9255248abff8@oracle.com"},"message":"ALSA: off by one bug in snd_riptide_joystick_probe()\n\ncommit e4940626defdf6c92da1052ad3f12741c1a28c90 upstream.\n\nThe problem here is that we check:\n\n\tif (dev >= SNDRV_CARDS)\n\nThen we increment \"dev\".\n\n       if (!joystick_port[dev++])\n\nThen we use it as an offset into a array with SNDRV_CARDS elements.\n\n\tif (!request_region(joystick_port[dev], 8, \"Riptide gameport\")) {\n\nThis has 3 effects:\n1) If you use the module option to specify the joystick port then it has\n   to be shifted one space over.\n2) The wrong error message will be printed on failure if you have over\n   32 cards.\n3) Static checkers will correctly complain that are off by one.\n\nFixes: db1005ec6ff8 ('ALSA: riptide - Fix joystick resource handling')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/984cc9c1ae6e5c17bd3d6221c1cb5a9a239325d8"},{"sha":"e4b26540cfb8c5a46266361753ceb8b8332a8509","author":{"name":"Adrian Knoth","email":"a46998b0b8da1bfb9915a608af880075c963865e@drcomp.erfurt.thur.de"},"message":"ALSA: hdspm - Constrain periods to 2 on older cards\n\ncommit f0153c3d948c1764f6c920a0675d86fc1d75813e upstream.\n\nRME RayDAT and AIO use a fixed buffer size of 16384 samples. With period\nsizes of 32-4096, this translates to 4-512 periods.\n\nThe older RME cards have a variable buffer size but require exactly two\nperiods.\n\nThis patch enforces nperiods=2 on those cards.\n\nSigned-off-by: Adrian Knoth <adi@drcomp.erfurt.thur.de>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/e4b26540cfb8c5a46266361753ceb8b8332a8509"},{"sha":"a4ea2971e44c71cc7856bcae932863752a99b03e","author":{"name":"Krzysztof Kozlowski","email":"fa33ff94ee78b0cc87406a1c5d4cb96cbd5b6ef8@samsung.com"},"message":"power_supply: 88pm860x: Fix leaked power supply on probe fail\n\ncommit 24727b45b484e8937dcde53fa8d1aa70ac30ec0c upstream.\n\nDriver forgot to unregister power supply if request_threaded_irq()\nfailed in probe(). In such case the memory associated with power supply\nleaked.\n\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nFixes: a830d28b48bf (\"power_supply: Enable battery-charger for 88pm860x\")\nSigned-off-by: Sebastian Reichel <sre@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/a4ea2971e44c71cc7856bcae932863752a99b03e"},{"sha":"743ac373976d91dd91a5d9ea14f742d672ef8128","author":{"name":"Jisheng Zhang","email":"341f2a38da9a97f1065bf2abf1ac84c149ee21c4@marvell.com"},"message":"mmc: sdhci-pxav3: fix setting of pdata->clk_delay_cycles\n\ncommit 14460dbaf7a5a0488963fdb8232ad5c8a8cca7b7 upstream.\n\nCurrent code checks \"clk_delay_cycles > 0\" to know whether the optional\n\"mrvl,clk_delay_cycles\" is set or not. But of_property_read_u32() doesn't\ntouch clk_delay_cycles if the property is not set. And type of\nclk_delay_cycles is u32, so we may always set pdata->clk_delay_cycles as a\nrandom value.\n\nThis patch fix this problem by check the return value of of_property_read_u32()\nto know whether the optional clk-delay-cycles is set or not.\n\nSigned-off-by: Jisheng Zhang <jszhang@marvell.com>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/743ac373976d91dd91a5d9ea14f742d672ef8128"},{"sha":"2cb0cdbc862644d6df784309178d706ea6da3dbc","author":{"name":"Jeff Layton","email":"0a799ee4f46e914219e7741adcc5e93178d519ec@primarydata.com"},"message":"nfs: don't call blocking operations while !TASK_RUNNING\n\ncommit 6ffa30d3f734d4f6b478081dfc09592021028f90 upstream.\n\nBruce reported seeing this warning pop when mounting using v4.1:\n\n     ------------[ cut here ]------------\n     WARNING: CPU: 1 PID: 1121 at kernel/sched/core.c:7300 __might_sleep+0xbd/0xd0()\n    do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffff810ff58f>] prepare_to_wait+0x2f/0x90\n    Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace sunrpc fscache ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer ppdev joydev snd virtio_console virtio_balloon pcspkr serio_raw parport_pc parport pvpanic floppy soundcore i2c_piix4 virtio_blk virtio_net qxl drm_kms_helper ttm drm virtio_pci virtio_ring ata_generic virtio pata_acpi\n    CPU: 1 PID: 1121 Comm: nfsv4.1-svc Not tainted 3.19.0-rc4+ #25\n    Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140709_153950- 04/01/2014\n     0000000000000000 000000004e5e3f73 ffff8800b998fb48 ffffffff8186ac78\n     0000000000000000 ffff8800b998fba0 ffff8800b998fb88 ffffffff810ac9da\n     ffff8800b998fb68 ffffffff81c923e7 00000000000004d9 0000000000000000\n    Call Trace:\n     [<ffffffff8186ac78>] dump_stack+0x4c/0x65\n     [<ffffffff810ac9da>] warn_slowpath_common+0x8a/0xc0\n     [<ffffffff810aca65>] warn_slowpath_fmt+0x55/0x70\n     [<ffffffff810ff58f>] ? prepare_to_wait+0x2f/0x90\n     [<ffffffff810ff58f>] ? prepare_to_wait+0x2f/0x90\n     [<ffffffff810dd2ad>] __might_sleep+0xbd/0xd0\n     [<ffffffff8124c973>] kmem_cache_alloc_trace+0x243/0x430\n     [<ffffffff810d941e>] ? groups_alloc+0x3e/0x130\n     [<ffffffff810d941e>] groups_alloc+0x3e/0x130\n     [<ffffffffa0301b1e>] svcauth_unix_accept+0x16e/0x290 [sunrpc]\n     [<ffffffffa0300571>] svc_authenticate+0xe1/0xf0 [sunrpc]\n     [<ffffffffa02fc564>] svc_process_common+0x244/0x6a0 [sunrpc]\n     [<ffffffffa02fd044>] bc_svc_process+0x1c4/0x260 [sunrpc]\n     [<ffffffffa03d5478>] nfs41_callback_svc+0x128/0x1f0 [nfsv4]\n     [<ffffffff810ff970>] ? wait_woken+0xc0/0xc0\n     [<ffffffffa03d5350>] ? nfs4_callback_svc+0x60/0x60 [nfsv4]\n     [<ffffffff810d45bf>] kthread+0x11f/0x140\n     [<ffffffff810ea815>] ? local_clock+0x15/0x30\n     [<ffffffff810d44a0>] ? kthread_create_on_node+0x250/0x250\n     [<ffffffff81874bfc>] ret_from_fork+0x7c/0xb0\n     [<ffffffff810d44a0>] ? kthread_create_on_node+0x250/0x250\n    ---[ end trace 675220a11e30f4f2 ]---\n\nnfs41_callback_svc does most of its work while in TASK_INTERRUPTIBLE,\nwhich is just wrong. Fix that by finishing the wait immediately if we've\nfound that the list has something on it.\n\nAlso, we don't expect this kthread to accept signals, so we should be\nusing a TASK_UNINTERRUPTIBLE sleep instead. That however, opens us up\nhung task warnings from the watchdog, so have the schedule_timeout\nwake up every 60s if there's no callback activity.\n\nReported-by: \"J. Bruce Fields\" <bfields@fieldses.org>\nSigned-off-by: Jeff Layton <jlayton@primarydata.com>\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/2cb0cdbc862644d6df784309178d706ea6da3dbc"},{"sha":"48eb2f280de57b705ef08b934bc3b1ac98ac26e4","author":{"name":"James Hogan","email":"00935fde11ed589f6e5a2cfc70182e355d2baa37@imgtec.com"},"message":"MIPS: KVM: Deliver guest interrupts after local_irq_disable()\n\ncommit 044f0f03eca0110e1835b2ea038a484b93950328 upstream.\n\nWhen about to run the guest, deliver guest interrupts after disabling\nhost interrupts. This should prevent an hrtimer interrupt from being\nhandled after delivering guest interrupts, and therefore not delivering\nthe guest timer interrupt until after the next guest exit.\n\nSigned-off-by: James Hogan <james.hogan@imgtec.com>\nCc: Paolo Bonzini <pbonzini@redhat.com>\nCc: Gleb Natapov <gleb@kernel.org>\nCc: kvm@vger.kernel.org\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: linux-mips@linux-mips.org\nCc: Sanjay Lal <sanjayl@kymasys.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: geiti94 <geiti94@me.com>","distinct":true,"url":"https://api.github.com/repos/geiti94/NEMESIS_KERNEL_N5/commits/48eb2f280de57b705ef08b934bc3b1ac98ac26e4"}]}
{"actor":{"display_login":"geiti94"}}