1. 18 1月, 2015 1 次提交
  2. 26 11月, 2014 1 次提交
    • P
      drm: imx: Move imx-drm driver out of staging · 6556f7f8
      Philipp Zabel 提交于
      The imx-drm driver was put into staging mostly for the following reasons,
      all of which have been addressed or superseded:
       - convert the irq driver to use linear irq domains
       - work out the device tree bindings, this lead to the common of_graph
         bindings being used
       - factor out common helper functions, this mostly resulted in the
         component framework and drm of_graph helpers.
      
      Before adding new fixes, and certainly before adding new features,
      move it into its proper place below drivers/gpu/drm.
      Signed-off-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      6556f7f8
  3. 20 10月, 2014 2 次提交
  4. 04 10月, 2014 2 次提交
  5. 01 10月, 2014 1 次提交
  6. 30 9月, 2014 1 次提交
  7. 24 9月, 2014 1 次提交
  8. 31 8月, 2014 1 次提交
    • G
      staging: remove nokia_hp4p driver · a4102f90
      Greg Kroah-Hartman 提交于
      The Bluetooth maintainer has been complaining about it for a while, and
      I shouldn't have merged it over his objections.  There also has been no
      real work done on it at all to get it out of the staging tree, so just
      delete the code for now.
      
      If someone wants to get this fixed up properly, feel free to revert this
      commit and send the revert, along with cleanups and we will be glad to
      consider it.
      
      Cc: Marcel Holtmann <marcel@holtmann.org>
      Cc: Pali Rohár <pali.rohar@gmail.com>
      Cc: Pavel Machek <pavel@ucw.cz>,
      Cc: Miguel Oliveira <cmroliv@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a4102f90
  9. 26 8月, 2014 1 次提交
  10. 28 7月, 2014 2 次提交
  11. 25 7月, 2014 2 次提交
  12. 24 7月, 2014 3 次提交
  13. 16 7月, 2014 1 次提交
    • K
      staging: tidspbridge: remove driver · f190be7f
      Kristina Martšenko 提交于
      The driver has been broken and disabled for several kernel versions now.
      It doesn't have a maintainer anymore, and most of the people who've
      worked on it have moved on. There's also still a long list of issues in
      the TODO file before it can be moved out of staging. Until someone can
      put in the work to make the driver work again and move it out of
      staging, remove it from the kernel.
      Signed-off-by: NKristina Martšenko <kristina.martsenko@gmail.com>
      Cc: Omar Ramirez Luna <omar.ramirez@copitl.com>
      Cc: Suman Anna <s-anna@ti.com>
      Cc: Felipe Contreras <felipe.contreras@gmail.com>
      Cc: Ohad Ben-Cohen <ohad@wizery.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      f190be7f
  14. 02 7月, 2014 1 次提交
  15. 01 7月, 2014 3 次提交
  16. 29 6月, 2014 1 次提交
  17. 20 6月, 2014 3 次提交
  18. 23 5月, 2014 2 次提交
  19. 26 4月, 2014 1 次提交
  20. 19 4月, 2014 1 次提交
  21. 17 4月, 2014 1 次提交
  22. 06 4月, 2014 1 次提交
  23. 05 3月, 2014 1 次提交
  24. 01 3月, 2014 3 次提交
  25. 08 2月, 2014 2 次提交
  26. 31 1月, 2014 1 次提交
    • M
      zram: promote zram from staging · cd67e10a
      Minchan Kim 提交于
      Zram has lived in staging for a LONG LONG time and have been
      fixed/improved by many contributors so code is clean and stable now.  Of
      course, there are lots of product using zram in real practice.
      
      The major TV companys have used zram as swap since two years ago and
      recently our production team released android smart phone with zram
      which is used as swap, too and recently Android Kitkat start to use zram
      for small memory smart phone.  And there was a report Google released
      their ChromeOS with zram, too and cyanogenmod have been used zram long
      time ago.  And I heard some disto have used zram block device for tmpfs.
      In addition, I saw many report from many other peoples.  For example,
      Lubuntu start to use it.
      
      The benefit of zram is very clear.  With my experience, one of the
      benefit was to remove jitter of video application with backgroud memory
      pressure.  It would be effect of efficient memory usage by compression
      but more issue is whether swap is there or not in the system.  Recent
      mobile platforms have used JAVA so there are many anonymous pages.  But
      embedded system normally are reluctant to use eMMC or SDCard as swap
      because there is wear-leveling and latency issues so if we do not use
      swap, it means we can't reclaim anoymous pages and at last, we could
      encounter OOM kill.  :(
      
      Although we have real storage as swap, it was a problem, too.  Because
      it sometime ends up making system very unresponsible caused by slow swap
      storage performance.
      
      Quote from Luigi on Google
       "Since Chrome OS was mentioned: the main reason why we don't use swap
        to a disk (rotating or SSD) is because it doesn't degrade gracefully
        and leads to a bad interactive experience.  Generally we prefer to
        manage RAM at a higher level, by transparently killing and restarting
        processes.  But we noticed that zram is fast enough to be competitive
        with the latter, and it lets us make more efficient use of the
        available RAM.  " and he announced.
      http://www.spinics.net/lists/linux-mm/msg57717.html
      
      Other uses case is to use zram for block device.  Zram is block device
      so anyone can format the block device and mount on it so some guys on
      the internet start zram as /var/tmp.
      http://forums.gentoo.org/viewtopic-t-838198-start-0.html
      
      Let's promote zram and enhance/maintain it instead of removing.
      Signed-off-by: NMinchan Kim <minchan@kernel.org>
      Reviewed-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Acked-by: NNitin Gupta <ngupta@vflare.org>
      Acked-by: NPekka Enberg <penberg@kernel.org>
      Cc: Bob Liu <bob.liu@oracle.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Hugh Dickins <hughd@google.com>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Luigi Semenzato <semenzato@google.com>
      Cc: Mel Gorman <mgorman@suse.de>
      Cc: Rik van Riel <riel@redhat.com>
      Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd67e10a