1. 08 Aug, 2014 1 commit
  2. 04 Aug, 2014 3 commits
    • Tomi Valkeinen's avatar
      be92abea
    • Dexuan Cui's avatar
      video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic · 3686fe96
      Dexuan Cui authored
      Currently the VSC has no chance to notify the VSP of the dirty rectangle on VM
      panic because the notification work is done in a workqueue, and in panic() the
      kernel typically ends up in an infinite loop, and a typical kernel config has
      CONFIG_PREEMPT_VOLUNTARY=y and CONFIG_PREEMPT is not set, so a context switch
      can't happen in panic() and the workqueue won't have a chance to run. As a
      result, the VM Connection window can't refresh until it's closed and we
      re-connect to the VM.
      
      We can register a handler on panic_notifier_list: the handler can notify
      the VSC and switch the framebuffer driver to a "synchronous mode", meaning
      the VSC flushes any future framebuffer change to the VSP immediately.
      
      v2: removed the MS-TFS line in the commit message
      v3: remove some 'unlikely' markings
      v4: avoid global variables as Tomi Valkeinen suggested
      
      Cc: Haiyang Zhang <haiyangz@microsoft.com>
      Signed-off-by: default avatarDexuan Cui <decui@microsoft.com>
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      3686fe96
    • Pawel Moll's avatar
      video: ARM CLCD: Fix DT-related build problems · 1d5167b7
      Pawel Moll authored
      This patch fixes the following error when !CONFIG_OF:
      
      drivers/video/fbdev/amba-clcd.c:800:54: warning: ‘struct amba_dev’ declared inside parameter list [enabled by default]
       static struct clcd_board *clcdfb_of_get_board(struct amba_dev *dev)
                                                            ^
      and adds a missing Kconfig select causing this
      when CONFIG_OF && !CONFIG_FB_MODE_HELPERS:
      
      drivers/video/fbdev/amba-clcd.c:567: undefined reference to `fb_videomode_from_videomode'
      Reported-by: default avatarFengguang Wu <fengguang.wu@intel.com>
      Signed-off-by: default avatarPawel Moll <pawel.moll@arm.com>
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      1d5167b7
  3. 30 Jul, 2014 1 commit
  4. 29 Jul, 2014 1 commit
  5. 04 Jul, 2014 17 commits
  6. 01 Jul, 2014 6 commits
  7. 26 Jun, 2014 1 commit
  8. 24 Jun, 2014 6 commits
  9. 22 Jun, 2014 4 commits
    • Linus Torvalds's avatar
      Linux 3.16-rc2 · a497c3ba
      Linus Torvalds authored
      a497c3ba
    • Linus Torvalds's avatar
      Merge branch 'i2c/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux · 8f5d2708
      Linus Torvalds authored
      Pull i2c new drivers from Wolfram Sang:
       "Here is a pull request from i2c hoping for the "new driver" rule.
      
        Originally, I wanted to send this request during the merge window, but
        code checkers with very recent additions complained, so a few fixups
        were needed.  So, some more time went by and I merged rc1 to get a
        stable base"
      
      So the "new driver" rule is really about drivers that people absolutely
      need for the kernel to work on new hardware, which is not so much the
      case for i2c.  So I considered not pulling this, but eventually
      relented.
      
      Just for FYI: the whole (and only) point of "new drivers" is not that
      new drivers cannot regress things (they can, and they have - by
      triggering badly tested code on machines that never triggered that code
      before), but because they can bring to life machines that otherwise
      wouldn't be useful at all without the drivers.
      
      So the new driver rule is for essential things that actual consumers
      would care about, ie devices like networking or disk drivers that matter
      to normal people (not server people - they run old kernels anyway, so
      mainlining new drivers is irrelevant for them).
      
      * 'i2c/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
        i2c: sun6-p2wi: fix call to snprintf
        i2c: rk3x: add NULL entry to the end of_device_id array
        i2c: sun6i-p2wi: use proper return value in probe
        i2c: sunxi: add P2WI (Push/Pull 2 Wire Interface) controller support
        i2c: sunxi: add P2WI DT bindings documentation
        i2c: rk3x: add driver for Rockchip RK3xxx SoC I2C adapter
      8f5d2708
    • Linus Torvalds's avatar
      Merge tag 'locks-v3.16-2' of git://git.samba.org/jlayton/linux · 2dfded82
      Linus Torvalds authored
      Pull file locking fixes from Jeff Layton:
       "File locking related bugfixes
      
        Nothing too earth-shattering here.  A fix for a potential regression
        due to a patch in pile #1, and the addition of a memory barrier to
        prevent a race condition between break_deleg and generic_add_lease"
      
      * tag 'locks-v3.16-2' of git://git.samba.org/jlayton/linux:
        locks: set fl_owner for leases back to current->files
        locks: add missing memory barrier in break_deleg
      2dfded82
    • Linus Torvalds's avatar
      Merge branch 'rc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild · 532f5138
      Linus Torvalds authored
      Pull kbuild fixes from Michal Marek:
       "There are three fixes for regressions caused by the relative paths
        series: deb-pkg, tar-pkg and *docs did not work with O=.
      
        Plus, there is a fix for the linux-headers deb package and a fixed
        typo.  These are not regression fixes but are safe enough"
      
      * 'rc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild:
        kbuild: fix a typo in a kbuild document
        builddeb: fix missing headers in linux-headers package
        Documentation: Fix DocBook build with relative $(srctree)
        kbuild: Fix tar-pkg with relative $(objtree)
        deb-pkg: Fix for relative paths
      532f5138