{"push_id":1100619811,"size":45,"distinct_size":45,"ref":"refs/heads/master","head":"07837831047fb72856d1f61a726a4094397facd8","before":"9caa7e78481f17fb6ff77dfaca774998e7440430","commits":[{"sha":"7ac7d19f808697abe6658c64c96868f728273f9c","author":{"email":"711c73f64afdce07b7e38039a96d2224209e9a6c@chris-wilson.co.uk","name":"Chris Wilson"},"message":"drm/i915: Avoid stalling on pending flips for legacy cursor updates\n\nThe legacy cursor ioctl expects to be asynchronous with respect to other\nscreen updates, in particular page flips. As X updates the cursor from a\nsignal context, if the cursor blocks then it will stall both the input\nand output chains causing bad stuttering and horrible UX.\n\nReported-and-tested-by: Rafael Ristovski <rafael.ristovski@gmail.com>\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94980\nFixes: 5008e874edd34 (\"drm/i915: Make wait_for_flips interruptible.\")\nSuggested-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>\nSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>\nCc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>\nCc: Ville Syrjälä <ville.syrjala@linux.intel.com>\nCc: Daniel Vetter <daniel.vetter@ffwll.ch>\nCc: Jani Nikula <jani.nikula@intel.com>\nCc: stable@vger.kernel.org\nLink: http://patchwork.freedesktop.org/patch/msgid/1460922166-20292-1-git-send-email-chris@chris-wilson.co.uk\nAcked-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nReviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>\n(cherry picked from commit acf4e84d6167317ff21be5c03e1ea76ea5783701)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/7ac7d19f808697abe6658c64c96868f728273f9c"},{"sha":"dab9a2663f4e688106c041f7cd2797a721382f0a","author":{"email":"fbd5edba1988036c8923f0cca0cce6ac4811db29@intel.com","name":"Imre Deak"},"message":"drm/i915: Fix system resume if PCI device remained enabled\n\nDuring system resume we depended on pci_enable_device() also putting the\ndevice into PCI D0 state. This won't work if the PCI device was already\nenabled but still in D3 state. This is because pci_enable_device() is\nrefcounted and will not change the HW state if called with a non-zero\nrefcount. Leaving the device in D3 will make all subsequent device\naccesses fail.\n\nThis didn't cause a problem most of the time, since we resumed with an\nenable refcount of 0. But it fails at least after module reload because\nafter that we also happen to leak a PCI device enable reference: During\nprobing we call drm_get_pci_dev() which will enable the PCI device, but\nduring device removal drm_put_dev() won't disable it. This is a bug of\nits own in DRM core, but without much harm as it only leaves the PCI\ndevice enabled. Fixing it is also a bit more involved, due to DRM\nmid-layering and because it affects non-i915 drivers too. The fix in\nthis patch is valid regardless of the problem in DRM core.\n\nv2:\n- Add a code comment about the relation of this fix to the freeze/thaw\n  vs. the suspend/resume phases. (Ville)\n- Add a code comment about the inconsistent ordering of set power state\n  and device enable calls. (Chris)\n\nCC: Ville Syrjälä <ville.syrjala@linux.intel.com>\nCC: Chris Wilson <chris@chris-wilson.co.uk>\nCC: stable@vger.kernel.org\nSigned-off-by: Imre Deak <imre.deak@intel.com>\nReviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nLink: http://patchwork.freedesktop.org/patch/msgid/1460979954-14503-1-git-send-email-imre.deak@intel.com\n(cherry picked from commit 44410cd0bfb26bde9288da34c190cc9267d42a20)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/dab9a2663f4e688106c041f7cd2797a721382f0a"},{"sha":"5eaa60c7109b40f17ac81090bc8b90482da76cd1","author":{"email":"fbd5edba1988036c8923f0cca0cce6ac4811db29@intel.com","name":"Imre Deak"},"message":"drm/i915/ddi: Fix eDP VDD handling during booting and suspend/resume\n\nThe driver's VDD on/off logic assumes that whenever the VDD is on we\nalso hold an AUX power domain reference. Since BIOS can leave the VDD on\nduring booting and resuming and on DDI platforms we won't take a\ncorresponding power reference, the above assumption won't hold on those\nplatforms and an eventual delayed VDD off work will do an extraneous AUX\npower domain put resulting in a refcount underflow. Fix this the same\nway we did this for non-DDI DP encoders:\n\ncommit 6d93c0c41760c0 (\"drm/i915: fix VDD state tracking after system\nresume\")\n\nAt the same time call the DP encoder suspend handler the same way as the\nnon-DDI DP encoders do to flush any pending VDD off work. Leaving the\nwork running may cause a HW access where we don't expect this (at a point\nwhere power domains are suspended already).\n\nWhile at it remove an unnecessary function call indirection.\n\nThis fixed for me AUX refcount underflow problems on BXT during\nsuspend/resume.\n\nCC: Ville Syrjälä <ville.syrjala@linux.intel.com>\nCC: stable@vger.kernel.org\nSigned-off-by: Imre Deak <imre.deak@intel.com>\nReviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nLink: http://patchwork.freedesktop.org/patch/msgid/1460963062-13211-4-git-send-email-imre.deak@intel.com\n(cherry picked from commit bf93ba67e9c05882f05b7ca2d773cfc8bf462c2a)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/5eaa60c7109b40f17ac81090bc8b90482da76cd1"},{"sha":"992e7a41f9fcc7bcd10e7d346aee5ed7a2c241cb","author":{"email":"37fffaeeafa52a2e0cb802ff3a2d512d52ac25a1@intel.com","name":"Mika Kahola"},"message":"drm/i915: Fix eDP low vswing for Broadwell\n\nIt was noticed on bug #94087 that module parameter\ni915.edp_vswing=2 that should override the VBT setting\nto use default voltage swing (400 mV) was not applied\nfor Broadwell.\n\nThis patch provides a fix for this by checking if default\ni.e. higher voltage swing is requested to be used and\napplies the DDI translations table for DP instead of eDP\n(low vswing) table.\n\nv2: Combine two if statements into one (Jani)\nv3: Change dev_priv->edp_low_vswing to use dev_priv->vbt.edp.low_vswing\n\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94087\nSigned-off-by: Mika Kahola <mika.kahola@intel.com>\nLink: http://patchwork.freedesktop.org/patch/msgid/1461155942-7749-1-git-send-email-mika.kahola@intel.com\nCc: stable@vger.kernel.org\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\n(cherry picked from commit 00983519214b61c1b9371ec2ed55a4dde773e384)\n[Jani: s/dev_priv->vbt.edp.low_vswing/dev_priv->edp_low_vswing/ to backport]\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/992e7a41f9fcc7bcd10e7d346aee5ed7a2c241cb"},{"sha":"60b3143c7cac7e8d2ca65c0b347466c5776395d1","author":{"email":"a727ff865dce73719e876e0c0ed5176fe771b234@intel.com","name":"Shashank Sharma"},"message":"drm/i915: Fake HDMI live status\n\nThis patch does the following:\n- Fakes live status of HDMI as connected (even if that's not).\n  While testing certain (monitor + cable) combinations with\n  various intel  platforms, it seems that live status register\n  doesn't work reliably on some older devices. So limit the\n  live_status check for HDMI detection, only for platforms\n  from gen7 onwards.\n\nV2: restrict faking live_status to certain platforms\nV3: (Ville)\n   - keep the debug message for !live_status case\n   - fix indentation of comment\n   - remove \"warning\" from the debug message\n\n    (Jani)\n   - Change format of fix details in the commit message\n\nFixes: 237ed86c693d (\"drm/i915: Check live status before reading edid\")\nCc: stable@vger.kernel.org # v4.4\nSuggested-by: Ville Syrjala <ville.syrjala@linux.intel.com>\nSigned-off-by: Shashank Sharma <shashank.sharma@intel.com>\nLink: http://patchwork.freedesktop.org/patch/msgid/1461237606-16491-1-git-send-email-shashank.sharma@intel.com\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\n(cherry picked from commit 4f4a8185011773f7520d9916c6857db946e7f9d1)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/60b3143c7cac7e8d2ca65c0b347466c5776395d1"},{"sha":"4ea3959018d09edfa36a9e7b5ccdbd4ec4b99e49","author":{"email":"cd6e8d405ca90be3a03d5427c5b24fbd2d68dcc4@linux.intel.com","name":"Ville Syrjälä"},"message":"drm/i915: Make RPS EI/thresholds multiple of 25 on SNB-BDW\n\nSomehow my SNB GT1 (Dell XPS 8300) gets very unhappy around\nGPU hangs if the RPS EI/thresholds aren't suitably aligned.\nIt seems like scheduling/timer interupts stop working somehow\nand things get stuck eg. in usleep_range().\n\nI bisected the problem down to\ncommit 8a5864377b12 (\"drm/i915/skl: Restructured the gen6_set_rps_thresholds function\")\nI observed that before all the values were at least multiples of 25,\nbut afterwards they are not. And rounding things up to the next multiple\nof 25 does seem to help, so lets' do that. I also tried roundup(..., 5)\nbut that wasn't sufficient. Also I have no idea if we might need this sort of\nthing on gen9+ as well.\n\nThese are the original EI/thresholds:\n LOW_POWER\n  GEN6_RP_UP_EI          12500\n  GEN6_RP_UP_THRESHOLD   11800\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 21250\n BETWEEN\n  GEN6_RP_UP_EI          10250\n  GEN6_RP_UP_THRESHOLD    9225\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 18750\n HIGH_POWER\n  GEN6_RP_UP_EI           8000\n  GEN6_RP_UP_THRESHOLD    6800\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 15000\n\nThese are after 8a5864377b12:\n LOW_POWER\n  GEN6_RP_UP_EI          12500\n  GEN6_RP_UP_THRESHOLD   11875\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 21250\n BETWEEN\n  GEN6_RP_UP_EI          10156\n  GEN6_RP_UP_THRESHOLD    9140\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 18750\n HIGH_POWER\n  GEN6_RP_UP_EI           7812\n  GEN6_RP_UP_THRESHOLD    6640\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 15000\n\nAnd these are what we have after this patch:\n LOW_POWER\n  GEN6_RP_UP_EI          12500\n  GEN6_RP_UP_THRESHOLD   11875\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 21250\n BETWEEN\n  GEN6_RP_UP_EI          10175\n  GEN6_RP_UP_THRESHOLD    9150\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 18750\n HIGH_POWER\n  GEN6_RP_UP_EI           7825\n  GEN6_RP_UP_THRESHOLD    6650\n  GEN6_RP_DOWN_EI        25000\n  GEN6_RP_DOWN_THRESHOLD 15000\n\nCc: stable@vger.kernel.org\nCc: Akash Goel <akash.goel@intel.com>\nCc: Chris Wilson <chris@chris-wilson.co.uk>\nTestcase: igt/kms_pipe_crc_basic/hang-read-crc-pipe-B\nFixes: 8a5864377b12 (\"drm/i915/skl: Restructured the gen6_set_rps_thresholds function\")\nSigned-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nLink: http://patchwork.freedesktop.org/patch/msgid/1461159836-9108-1-git-send-email-ville.syrjala@linux.intel.com\nAcked-by: Chris Wilson <chris@chris-wilson.co.uk>\nReviewed-by: Patrik Jakobsson <patrik.jakobsson@linux.intel.com>\n(cherry picked from commit 8a292d016d1cc4938ff14b4df25328230b08a408)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/4ea3959018d09edfa36a9e7b5ccdbd4ec4b99e49"},{"sha":"0224a4a30b57385a60065aa598181868881d8fc6","author":{"email":"0364a60538b3766c953bdea7e7e4859afd98436c@linux.intel.com","name":"Heikki Krogerus"},"message":"device property: Avoid potential dereferences of invalid pointers\n\nSince fwnode may hold ERR_PTR(-ENODEV) or it may be NULL,\nthe fwnode type checks is_of_node(), is_acpi_node() and is\nis_pset_node() need to consider it. Using IS_ERR_OR_NULL()\nto check it.\n\nFixes: 0d67e0fa1664 (device property: fix for a case of use-after-free)\nReported-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>\n[ rjw: Subject & changelog ]\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/0224a4a30b57385a60065aa598181868881d8fc6"},{"sha":"2548d546d40c0014efdde88a53bf7896e917dcce","author":{"email":"3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","name":"Peter Zijlstra"},"message":"nohz/full, sched/rt: Fix missed tick-reenabling bug in sched_can_stop_tick()\n\nChris Metcalf reported a that sched_can_stop_tick() sometimes fails to\nre-enable the tick.\n\nHis observed problem is that rq->cfs.nr_running can be 1 even though\nthere are multiple runnable CFS tasks. This happens in the cgroup\ncase, in which case cfs.nr_running is the number of runnable entities\nfor that level.\n\nIf there is a single runnable cgroup (which can have an arbitrary\nnumber of runnable child entries itself) rq->cfs.nr_running will be 1.\n\nHowever, looking at that function I think there's more problems with it.\n\nIt seems to assume that if there's FIFO tasks, those will run. This is\nincorrect. The FIFO task can have a lower prio than an RR task, in which\ncase the RR task will run.\n\nSo the whole fifo_nr_running test seems misplaced, it should go after\nthe rr_nr_running tests. That is, only if !rr_nr_running, can we use\nfifo_nr_running like this.\n\nReported-by: Chris Metcalf <cmetcalf@mellanox.com>\nTested-by: Chris Metcalf <cmetcalf@mellanox.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Christoph Lameter <cl@linux.com>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Luiz Capitulino <lcapitulino@redhat.com>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Rik van Riel <riel@redhat.com>\nCc: Stephane Eranian <eranian@google.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Vince Weaver <vincent.weaver@maine.edu>\nCc: Viresh Kumar <viresh.kumar@linaro.org>\nCc: Wanpeng Li <kernellwp@gmail.com>\nFixes: 76d92ac305f2 (\"sched: Migrate sched to use new tick dependency mask model\")\nLink: http://lkml.kernel.org/r/20160421160315.GK24771@twins.programming.kicks-ass.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/2548d546d40c0014efdde88a53bf7896e917dcce"},{"sha":"625fe4f8ffc1b915248558481bb94249f6bd411c","author":{"email":"ebe5c4842edd72edc3a105fa34a4e41fed7a97bc@arm.com","name":"James Morse"},"message":"ARM: cpuidle: Pass on arm_cpuidle_suspend()'s return value\n\narm_cpuidle_suspend() may return -EOPNOTSUPP, or any value returned\nby the cpu_ops/cpuidle_ops suspend call. arm_enter_idle_state() doesn't\nupdate 'ret' with this value, meaning we always signal success to\ncpuidle_enter_state(), causing it to update the usage counters as if we\nsucceeded.\n\nFixes: 191de17aa3c1 (\"ARM64: cpuidle: Replace cpu_suspend by the common ARM/ARM64 function\")\nSigned-off-by: James Morse <james.morse@arm.com>\nAcked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>\nAcked-by: Daniel Lezcano <daniel.lezcano@linaro.org>\nCc: 4.1+ <stable@vger.kernel.org> # 4.1+\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/625fe4f8ffc1b915248558481bb94249f6bd411c"},{"sha":"2482bc31ca8096241b8fa97610ef23154ce55f45","author":{"email":"3182c67ddb20f5f99c41c1db124f5e366fe161c5@arm.com","name":"Sudeep Holla"},"message":"cpufreq: st: enable selective initialization based on the platform\n\nThe sti-cpufreq does unconditional registration of the cpufreq-dt driver\nwhich causes issue on an multi-platform build. For example, on Vexpress\nTC2 platform, we get the following error on boot:\n\ncpu cpu0: OPP-v2 not supported\ncpu cpu0: Not doing voltage scaling\ncpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table\n\tfor cpu:0, -19\ncpu cpu0: dev_pm_opp_get_max_volt_latency: Invalid regulator (-6)\n...\narm_big_little: bL_cpufreq_register: Failed registering platform driver:\n\t\tvexpress-spc, err: -17\n\nThe actual driver fails to initialise as cpufreq-dt is probed\nsuccessfully, which is incorrect. This issue can happen to any platform\nnot using cpufreq-dt in a multi-platform build.\n\nThis patch adds a check to do selective initialization of the driver.\n\nFixes: ab0ea257fc58 (cpufreq: st: Provide runtime initialised driver for ST's platforms)\nSigned-off-by: Sudeep Holla <sudeep.holla@arm.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nAcked-by: Lee Jones <lee.jones@linaro.org>\nCc: 4.5+ <stable@vger.kernel.org> # 4.5+\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/2482bc31ca8096241b8fa97610ef23154ce55f45"},{"sha":"b4c112114aab9aff5ed4568ca5e662bb02cdfe74","author":{"email":"14deb5e5e417133e888bf47bb6a3555c9bb7d81c@samba.org","name":"Anton Blanchard"},"message":"powerpc: Fix bad inline asm constraint in create_zero_mask()\n\nIn create_zero_mask() we have:\n\n\taddi\t%1,%2,-1\n\tandc\t%1,%1,%2\n\tpopcntd\t%0,%1\n\nusing the \"r\" constraint for %2. r0 is a valid register in the \"r\" set,\nbut addi X,r0,X turns it into an li:\n\n\tli\tr7,-1\n\tandc\tr7,r7,r0\n\tpopcntd\tr4,r7\n\nFix this by using the \"b\" constraint, for which r0 is not a valid\nregister.\n\nThis was found with a kernel build using gcc trunk, narrowed down to\nwhen -frename-registers was enabled at -O2. It is just luck however\nthat we aren't seeing this on older toolchains.\n\nThanks to Segher for working with me to find this issue.\n\nCc: stable@vger.kernel.org\nFixes: d0cebfa650a0 (\"powerpc: word-at-a-time optimization for 64-bit Little Endian\")\nSigned-off-by: Anton Blanchard <anton@samba.org>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/b4c112114aab9aff5ed4568ca5e662bb02cdfe74"},{"sha":"ba41e1bc28bd862089b0fc00e8136aa258a62b21","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"cpufreq: intel_pstate: Fix HWP on boot CPU after system resume\n\nCommit 41cfd64cf49fc \"Update frequencies of policy->cpus only from\n->set_policy()\" changed the way the intel_pstate driver's ->set_policy\ncallback updates the HWP (hardware-managed P-states) settings.\nA side effect of it is that if those settings are modified on the\nboot CPU during system suspend and wakeup, they will never be\nrestored during subsequent system resume.\n\nTo address this problem, allow cpufreq drivers that don't provide\n->target or ->target_index callbacks to use ->suspend and ->resume\ncallbacks and add a ->resume callback to intel_pstate to restore\nthe HWP settings on the CPUs that belong to the given policy.\n\nFixes: 41cfd64cf49fc \"Update frequencies of policy->cpus only from ->set_policy()\"\nTested-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/ba41e1bc28bd862089b0fc00e8136aa258a62b21"},{"sha":"0092d3edcb23fcdb8cbe4159ba94a534290ff982","author":{"email":"f2295d84e358395675bc8031be58672073ae065e@redhat.com","name":"Dave Airlie"},"message":"drm/amdgpu: set metadata pointer to NULL after freeing.\n\nWithout this there was a double free of the metadata,\nwhich ended up freeing the fd table for me here, and taking\nout the machine more often than not.\n\nI reproduced with X.org + modesetting DDX + latest llvm/mesa,\nalso required using dri3.\n\nCc: stable@vger.kernel.org\nReviewed-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: Dave Airlie <airlied@redhat.com>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/0092d3edcb23fcdb8cbe4159ba94a534290ff982"},{"sha":"3104b8128d4d646a574ed9d5b17c7d10752cd70b","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/radeon: make sure vertical front porch is at least 1\n\nhw doesn't like a 0 value.\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/3104b8128d4d646a574ed9d5b17c7d10752cd70b"},{"sha":"0126d4b9a516256f2432ca0dc78ab293a8255378","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/amdgpu: make sure vertical front porch is at least 1\n\nhw doesn't like a 0 value.\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/0126d4b9a516256f2432ca0dc78ab293a8255378"},{"sha":"e8dfe6d8f6762d515fcd4f30577f7bfcf7659887","author":{"email":"1fa2ef4755a9226cb9a0a4840bd89b158ac71391@codeblueprint.co.uk","name":"Matt Fleming"},"message":"MAINTAINERS: Remove asterisk from EFI directory names\n\nMark reported that having asterisks on the end of directory names\nconfuses get_maintainer.pl when it encounters subdirectories, and that\nmy name does not appear when run on drivers/firmware/efi/libstub.\n\nReported-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Matt Fleming <matt@codeblueprint.co.uk>\nCc: <stable@vger.kernel.org>\nCc: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-efi@vger.kernel.org\nLink: http://lkml.kernel.org/r/1462303781-8686-2-git-send-email-matt@codeblueprint.co.uk\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/e8dfe6d8f6762d515fcd4f30577f7bfcf7659887"},{"sha":"7f9b474c92713067237c8188f32791cc4007b5da","author":{"email":"94755a79aca753e683bb6d0e796d473b797056eb@fedoraproject.org","name":"Josh Boyer"},"message":"x86/efi-bgrt: Switch all pr_err() to pr_notice() for invalid BGRT\n\nThe promise of pretty boot splashes from firmware via BGRT was at\nbest only that; a promise.  The kernel diligently checks to make\nsure the BGRT data firmware gives it is valid, and dutifully warns\nthe user when it isn't.  However, it does so via the pr_err log\nlevel which seems unnecessary.  The user cannot do anything about\nthis and there really isn't an error on the part of Linux to\ncorrect.\n\nThis lowers the log level by using pr_notice instead.  Users will\nno longer have their boot process uglified by the kernel reminding\nus that firmware can and often is broken when the 'quiet' kernel\nparameter is specified.  Ironic, considering BGRT is supposed to\nmake boot pretty to begin with.\n\nSigned-off-by: Josh Boyer <jwboyer@fedoraproject.org>\nSigned-off-by: Matt Fleming <matt@codeblueprint.co.uk>\nReviewed-by: Josh Triplett <josh@joshtriplett.org>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Brian Gerst <brgerst@gmail.com>\nCc: Denys Vlasenko <dvlasenk@redhat.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Môshe van der Sterre <me@moshe.nl>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-efi@vger.kernel.org\nLink: http://lkml.kernel.org/r/1462303781-8686-4-git-send-email-matt@codeblueprint.co.uk\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/7f9b474c92713067237c8188f32791cc4007b5da"},{"sha":"6d45b719cbd51f014bb1b5dd8ed99068d78d36af","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"intel_pstate: Fix intel_pstate_get()\n\nAfter commit 8fa520af5081 \"intel_pstate: Remove freq calculation from\nintel_pstate_calc_busy()\" intel_pstate_get() calls get_avg_frequency()\nto compute the average frequency, which is problematic for two reasons.\n\nFirst, intel_pstate_get() may be invoked before the driver reads the\nCPU feedback registers for the first time and if that happens,\nget_avg_frequency() will attempt to divide by zero.\n\nSecond, the get_avg_frequency() call in intel_pstate_get() is racy\nwith respect to intel_pstate_sample() and it may end up returning\ncompletely meaningless values for this reason.\n\nMoreover, after commit 7349ec0470b6 \"intel_pstate: Move\nintel_pstate_calc_busy() into get_target_pstate_use_performance()\"\nsample.core_pct_busy is never computed on Atom, but it is used in\nintel_pstate_adjust_busy_pstate() in that case too.\n\nTo address those problems notice that if sample.core_pct_busy\nwas used in the average frequency computation carried out by\nget_avg_frequency(), both the divide by zero problem and the\nrace with respect to intel_pstate_sample() would be avoided.\n\nAccordingly, move the invocation of intel_pstate_calc_busy() from\nget_target_pstate_use_performance() to intel_pstate_update_util(),\nwhich also will take care of the uninitialized sample.core_pct_busy\non Atom, and modify get_avg_frequency() to use sample.core_pct_busy\nas per the above.\n\nReported-by: kernel test robot <ying.huang@linux.intel.com>\nLink: http://marc.info/?l=linux-kernel&m=146226437623173&w=4\nFixes: 8fa520af5081 \"intel_pstate: Remove freq calculation from intel_pstate_calc_busy()\"\nFixes: 7349ec0470b6 \"intel_pstate: Move intel_pstate_calc_busy() into get_target_pstate_use_performance()\"\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/6d45b719cbd51f014bb1b5dd8ed99068d78d36af"},{"sha":"93d68841a23a5779cef6fb9aa0ef32e7c5bd00da","author":{"email":"fe4655370dc87a32329d591d6e8472329333dfad@redhat.com","name":"Prarit Bhargava"},"message":"ACPICA: Dispatcher: Update thread ID for recursive method calls\n\nACPICA commit 7a3bd2d962f221809f25ddb826c9e551b916eb25\n\nSet the mutex owner thread ID.\nOriginal patch from: Prarit Bhargava <prarit@redhat.com>\n\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=115121\nLink: https://github.com/acpica/acpica/commit/7a3bd2d9\nSigned-off-by: Prarit Bhargava <prarit@redhat.com>\nTested-by: Andy Lutomirski <luto@kernel.org> # On a Dell XPS 13 9350\nSigned-off-by: Bob Moore <robert.moore@intel.com>\nSigned-off-by: Lv Zheng <lv.zheng@intel.com>\nCc: All applicable <stable@vger.kernel.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/93d68841a23a5779cef6fb9aa0ef32e7c5bd00da"},{"sha":"21f8a99ce61b2d4b74bd425a5bf7e9efbe162788","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"PM / OPP: Remove useless check\n\nRegulators are optional for devices using OPPs and the OPP core\nshouldn't be printing any errors for such missing regulators.\n\nIt was fine before the commit 0c717d0f9cb4, but that failed to update\nthis part of the code to remove an 'always true' check and an extra\nunwanted print message.\n\nFix that now.\n\nFixes: 0c717d0f9cb4 (PM / OPP: Initialize regulator pointer to an error value)\nReported-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Stephen Boyd <sboyd@codeaurora.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/nmenon/linux-2.6-playground/commits/21f8a99ce61b2d4b74bd425a5bf7e9efbe162788"}]}