1. 02 May, 2019 1 commit
    • Antonio Borneo's avatar
      log: remove "%m" from format strings by using strerror(errno) · 39578636
      Antonio Borneo authored
      The printf() format specifier "%m" is a glibc extension to print
      the string returned by strerror(errno). While supported by other
      libraries (e.g. uClibc and musl), it is not widely portable.
      
      In Weston code the format string is often passed to a logging
      function that calls other syscalls before the conversion of "%m"
      takes place. If one of such syscall modifies the value in errno,
      the conversion of "%m" will incorrectly report the error string
      corresponding to the new value of errno.
      
      Remove all the occurrences of the specifier "%m" in Weston code
      by using directly the string returned by strerror(errno).
      While there, fix some minor indentation issue.
      Signed-off-by: Antonio Borneo's avatarAntonio Borneo <borneo.antonio@gmail.com>
      39578636
  2. 15 Jun, 2015 1 commit
  3. 15 May, 2015 1 commit
    • Michael Vetter's avatar
      remove trailing whitespaces · 2a18a528
      Michael Vetter authored
      Remove trailing whitespaces because they are not needed and jumping to
      the end of al ine should do just that and not jump to the whitespace.
      2a18a528
  4. 18 Aug, 2014 1 commit
    • Ryo Munakata's avatar
      gears: fix invalid calculation of the first FPS · a3a5debe
      Ryo Munakata authored
      At the calculation of the first FPS, gears has initialized last
      FPS time with gettimeofday().
      But the callback_data passed in the callback of wl_surface_frame()
      is the current time, in milliseconds, with an undefined base.
      Because of this subtracting last FPS time from callback_data makes no sense.
       For example, below is the result of running weston-gears on weston with
      drm backend:
      
      $ weston-gears
      Warning: FPS count is limited by the wayland compositor or monitor refresh rate
      1 frames in 1094460.125 seconds =  0.000 FPS
      301 frames in  5.016 seconds = 60.008 FPS
      301 frames in  5.016 seconds = 60.008 FPS
      301 frames in  5.016 seconds = 60.008 FPS
      
      As you can see, the the first FPS value is something odd.
      
      This patch fixes it by initializing last FPS time with the callback_data passed in
      the first callback.
      Reviewed-by: default avatarNils Chr. Brause <nilschrbrause@gmail.com>
      a3a5debe
  5. 24 Jun, 2014 1 commit
  6. 22 Oct, 2013 1 commit
  7. 08 Aug, 2013 1 commit
  8. 20 Feb, 2013 1 commit
  9. 27 Jul, 2012 3 commits
  10. 25 Jul, 2012 1 commit
  11. 31 May, 2012 1 commit
  12. 26 May, 2012 2 commits
  13. 22 May, 2012 1 commit
  14. 11 May, 2012 1 commit
  15. 10 May, 2012 1 commit
  16. 08 May, 2012 1 commit
  17. 07 May, 2012 2 commits
  18. 25 Apr, 2012 1 commit
  19. 30 Mar, 2012 1 commit
  20. 12 Mar, 2012 1 commit
    • Kristian H. Kristensen's avatar
      Add an option parser · bcacef19
      Kristian H. Kristensen authored
      On one hand, getopt (in particular the -o suboption syntax) sucks on the
      server side, and on the client side we would like to avoid the glib
      dependency.  We can roll out own option parser and solve both problems
      and save a few lines of code total.
      bcacef19
  21. 23 Feb, 2012 1 commit
  22. 13 Feb, 2012 1 commit
  23. 31 Jan, 2012 1 commit
  24. 19 Jan, 2012 1 commit
  25. 11 Jan, 2012 2 commits
  26. 10 Jan, 2012 2 commits
  27. 22 Nov, 2011 2 commits
  28. 07 Oct, 2011 2 commits
  29. 19 Sep, 2011 1 commit
  30. 29 Aug, 2011 3 commits